Hi JMS provider itself should be configurable to handle unavailability - check AMQ doc - so not sure it does worth using a request scoped bean.
Queue/topic are optional and generally you define them only when default doesnt match Romain Manni-Bucau @rmannibucau http://www.tomitribe.com http://rmannibucau.wordpress.com https://github.com/rmannibucau 2015-01-28 13:19 GMT+01:00 hwaastad <[email protected]>: > Hi, > just need to discuss with y'all kind of "best practice" when it comes to JMS > producers. > > Right now I'm producing connection/session/Messageproducer as > @Requestscoped. > Is there a reason for NOT doing so? > (Only way to get service availability on remote JMS, if its unavailable). > > So, another question, might be dumb, but anyway. > > In tomee, factory, adapter and mdcontainer config I get, however queue > resources, are they really needed? > > br hw > > > > > > -- > View this message in context: > http://tomee-openejb.979440.n4.nabble.com/JMS-Producers-not-strictly-TomEE-tp4673587.html > Sent from the TomEE Users mailing list archive at Nabble.com.
