On Wed, Aug 26, 2015 at 11:09 AM, Romain Manni-Bucau
<rmannibucau(a)gmail.com> wrote:
Agree for provided scope but JMS + short time scopes will not match
well in
practise so i would worry more about not "default" scopes which can miss
these events.
Short lived scopes like @RequestScoped may not be the best match indeed.
Additionally, @RequestScoped is kinda assumed to be an "@ThreadScoped"
thing, e.g. there's the expectation that only the current thread will
access it. If the JMS provider will asynchronously call a method on
the bean instance from another thread, then this breaks this
assumption.