Tom Akehurst

Added in 0.9.0

I think a flag for each is the way to do it, but you could change `SnapshotStubMappingGenerator` so that it just takes the whole `RecordSpec` object as a parameter instead...

Thanks for contributing this. I'm going to hold off merging it though, as we plan to expand WireMock's core model for streaming/multi chunk responses and then utilise this for gRPC...

OK, that's fair enough, but let's find a way to enable this explicitly rather than it being the default behaviour when there's a streamed response defined. I suggest adding a...

Could we make the name explicitly indicate that the body patterns would be merged rather than replaced? Or add an overload of `like()` taking a parameter to indicate this?

What's the benefit of returning to this approach, given that you got it to work without?

I'd quite like to get rid of the dependence on servlet contexts completely in WM. Seems pointless to still be coupled to it in 2024, and it makes it harder...

I can't replicate this. Can you create a repro project?

Thanks for sharing this. I see the issue now but it seems it's going to be a pain to fix as it's due to a change in the way Jetty...

This looks like a breaking change and has no test associated. Maybe it'd be better to extend the interface so that both the name and filename are accessible.