I'm actually inclined to *remove* some of these "convenience" methods. We
already have a client API which is well tested and well documented. I'm not
sure this additional layer for testing is doing a lot of good in the long
run. But I digress.
Justin
On Sat, Aug 19, 2023 at 11:10 AM Clebert Suco
Or you / we could add a new method with the old semantic with a clear doc
about it.
Alrhoufht I’m not sure what good is to keep the consumer leaking.
On Sat, Aug 19, 2023 at 10:53 AM Justin Bertram wrote:
> The behavior you're seeing is expected at this point given the fix for
> ARTEMIS-4234 [1
The behavior you're seeing is expected at this point given the fix for
ARTEMIS-4234 [1]. The capabilities of the JUnit resources are very basic,
and it doesn't really make sense to make them support more complex
use-cases when the client API already does this. Therefore you just need to
create your
YOu need to have the consumer and session open to be able to saveToOuptutStream
On your case, your using the core API directly and you're calling save
after the consumer closed. The change you mentioned is closing the
consumer.
I suggest you either use the consumer directly and close it yourself
