Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jms-dev] JMSContext Scoping
Hi Jonathan,

Thanks for posting this problem/solution.  I don't feel strongly enough about it to say one way or the other.  Sounds reasonable to me.  Can you put it in the https://github.com/jms-spec/jms-proposals? That way we can refer back to it later.

Richard

On Wed, Dec 12, 2018 at 8:44 AM Jonathan S. Fisher <exabrial+eclipse@xxxxxxxxx> wrote:
The JMS 2.0 spec left a pretty big hole in the spec with JMSContext. Essentially, the spec says JMSContext should be request scoped, or tx scoped, but doesn't give any guidance beyond that. There are plenty of times (ironically, one of them being from an MDB) where you have neither request scope or tx scope active.

I would propose the JMSContext stay TX scoped first, then request scoped if theres no ongoing transaction, then @Dependent scoped as a safe default if the other two are not available.

cheers,
-Jonathan
_______________________________________________
jms-dev mailing list
jms-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jms-dev


--

Back to the top