Daniel López wrote: > Hi Scott, > > I'm still using 3.1.*, is JMS in those versions production ready? > Documentation is a bit scarce so I'm not sure what to think of it. :) > Because the 4.0 version is an entire rewrite (to match our new clustering model), I think we'd rather have new Resin JMS users on the 4.0 and not the 3.1 branch. If you're on the 3.1 branch and evaluating it, you might look at a different solution because it would be more difficult to support 3.1 JMS (and any bugs/suggestions wouldn't help 4.0.)
-- Scott > D. > Scott Ferguson escribió: > >> Daniel López wrote: >> >>> Hi there, >>> >>> Nobody uses Resin's JMS from external applications? Do people use >>> other JMS solutions inside Resin? >>> I'll stick with OpenJMS for now, but as we already have Resin nodes >>> installed, I thought it would have been intesting to use them and >>> remove one service. >>> >>> The scarce documentation and apparent lack of usage is making me think >>> twice :). >>> >> The 4.0.x JMS is very new, since we rewrote it to use BAM and the >> underlying model. I do think we need another pass through that >> implementation before we declare it production ready. >> >> -- Scott >> >>> D. >>> >>> ------------------------------------------------------------------------ >>> >>> Subject: >>> [Resin-interest] Resin: configuration for a jms client >>> From: >>> Daniel López <d.lo...@uib.es> >>> Date: >>> Tue, 12 Jan 2010 14:37:09 +0100 >>> To: >>> General Discussion for the Resin application server >>> <resin-interest@caucho.com> >>> >>> To: >>> General Discussion for the Resin application server >>> <resin-interest@caucho.com> >>> >>> >>> While we are talking about JMS configuration, how can one access the JMS >>> queues on a Resin server from an external client? >>> >>> I've seen the documentation regarding accessing the queues defined in >>> the same server, from JSPs, using dependency injection etc. but I have >>> been unable to find how to access the queues from another JVM. >>> >>> I'm guessing one would need to configure access to the JMS queues >>> through hessian/burlap? And then what would be the appropriate >>> JNDI_PROVIDER_URL and INITIAL_CONTEXT_FACTORY formats? >>> >>> Thanks, >>> D. >>> > > > _______________________________________________ > resin-interest mailing list > resin-interest@caucho.com > http://maillist.caucho.com/mailman/listinfo/resin-interest > > _______________________________________________ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
