A MDB as well ;)
Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber <http://www.tomitribe.com> 2015-10-28 16:33 GMT+01:00 Jonathan S. Fisher < [email protected]>: > Yep, we can't wait till 7.x is released! We're hoping this year?? :D :D > > Actually, I just had another thought. A Stateless EJB is pretty much the > same thing as @TransactionScoped, is it not? > > @Stateless > @TransactionAttribute(TransactionAttributeType.REQUIRED) > public class JmsContext { > } > > > > > *Jonathan S. Fisher* > *VP - Information Technology* > *Spring Venture Group* > (o) 913-653-8820 > > On Tue, Oct 27, 2015 at 12:27 PM, Romain Manni-Bucau < > [email protected]> > wrote: > > > note sure if it was only for releases or more generally so saying it > > anyway: it is in 7.x > > > > > > Romain Manni-Bucau > > @rmannibucau <https://twitter.com/rmannibucau> | Blog > > <http://rmannibucau.wordpress.com> | Github < > > https://github.com/rmannibucau> | > > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber > > <http://www.tomitribe.com> > > > > 2015-10-27 18:25 GMT+01:00 Jonathan S. Fisher < > > [email protected]>: > > > > > I suppose we could implement it that way... Have a @Produces > > > @TransactionScoped on an JMS Session object. hmm. > > > > > > Too bad no @TransactionScoped in TomEE at the moment :( > > > > > > On Tue, Oct 27, 2015 at 11:31 AM, Romain Manni-Bucau < > > > [email protected]> > > > wrote: > > > > > > > Hi Jonathan, > > > > > > > > if I followed you just want @TransactionScoped? > > > > > > > > > > > > > > > > Romain Manni-Bucau > > > > @rmannibucau <https://twitter.com/rmannibucau> | Blog > > > > <http://rmannibucau.wordpress.com> | Github < > > > > https://github.com/rmannibucau> | > > > > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber > > > > <http://www.tomitribe.com> > > > > > > > > 2015-10-27 17:21 GMT+01:00 Jonathan S. Fisher < > > > > [email protected]>: > > > > > > > > > We have container managed EntityManagers bound to the current > > > > transaction, > > > > > why not container managed messaging context bound to the current > > > > > transaction? > > > > > > > > > > Has the JEE expert group ever discussed this? Just curious. > > > > > > > > > > -Jonathan > > > > > > > > > > -- > > > > > Email Confidentiality Notice: The information contained in this > > > > > transmission is confidential, proprietary or privileged and may be > > > > subject > > > > > to protection under the law, including the Health Insurance > > Portability > > > > and > > > > > Accountability Act (HIPAA). The message is intended for the sole > use > > of > > > > the > > > > > individual or entity to whom it is addressed. If you are not the > > > intended > > > > > recipient, you are notified that any use, distribution or copying > of > > > the > > > > > message is strictly prohibited and may subject you to criminal or > > civil > > > > > penalties. If you received this transmission in error, please > contact > > > the > > > > > sender immediately by replying to this email and delete the > material > > > from > > > > > any computer. > > > > > > > > > > > > > > > -- > > > Email Confidentiality Notice: The information contained in this > > > transmission is confidential, proprietary or privileged and may be > > subject > > > to protection under the law, including the Health Insurance Portability > > and > > > Accountability Act (HIPAA). The message is intended for the sole use of > > the > > > individual or entity to whom it is addressed. If you are not the > intended > > > recipient, you are notified that any use, distribution or copying of > the > > > message is strictly prohibited and may subject you to criminal or civil > > > penalties. If you received this transmission in error, please contact > the > > > sender immediately by replying to this email and delete the material > from > > > any computer. > > > > > > > -- > Email Confidentiality Notice: The information contained in this > transmission is confidential, proprietary or privileged and may be subject > to protection under the law, including the Health Insurance Portability and > Accountability Act (HIPAA). The message is intended for the sole use of the > individual or entity to whom it is addressed. If you are not the intended > recipient, you are notified that any use, distribution or copying of the > message is strictly prohibited and may subject you to criminal or civil > penalties. If you received this transmission in error, please contact the > sender immediately by replying to this email and delete the material from > any computer. >
