Thanks for the input, both of you. I will take a look at the activity in the repository and also inquire on the lists, as well as trying different implementations.
I'm curious. I know that, being open source, the Tomcat project generally welcomes volunteers who want to contribute features or improvements. However, I'd like to know at what point a feature is unwelcome in Tomcat. I know that Tomcat is not and does not desire to be a full JavaEE application server. So, with that in mind, does the community desire that Tomcat NOT ever have JMS implemented in it? Or, has it just never been done because nobody did it, and if a volunteer came along willing to implement JMS in Tomcat, would the community be open to that? Nick -----Original Message----- From: Daniel Mikusa [mailto:dmik...@vmware.com] Sent: Wednesday, January 30, 2013 12:51 PM To: Tomcat Users List Subject: Re: JMS in a Tomcat Environment On Jan 30, 2013, at 1:08 PM, Williams, Nick wrote: > I do not have a preferred implementation, no. I understand the basics of JMS > and how it works, but I have never actually used it before. I would second Chris' suggestion that you do a POC and try a few different implementations. Find the one that works best for your needs. > I do usually work with Spring Framework, but my understanding is that it's > relatively agnostic as to the underlying implementation of JMS. As is the JMS api. Either way, your code shouldn't need to change much, if at all, as you try different implementations. > ActiveMQ looks interesting. One concern I have is that some of the > documentation seems rather dated: referring to JavaEE 1.4, for example, when > 1.6 came out two years ago and 1.7 is on the brink of approval. And then > there's the context resource definition on the Tomcat page and references to > the shared lib directory, and immediately below that an 'updated' resource > definition for "Tomcat 5.5 or later" that's "completely untested but should > work." Seeing as how 6.0 and 7.0 are both mature and 8.0 is around the corner > somewhere, this seems awfully dated. I agree with you here. The Tomcat integration docs are very out-of-date. That said, my experience with the rest of their docs has been OK. > How well-maintained and up-to-date is ActiveMQ? Can we expect work on the > impending JMS 2.0 specification to begin any time in the future? To answer this question, I would suggest you look to their mailing lists and their code repository. You can see how often they check in code and how active the developers are on the mailing list. Dan > > Thanks, > > Nick > > -----Original Message----- > From: Daniel Mikusa [mailto:dmik...@vmware.com] > Sent: Wednesday, January 30, 2013 11:41 AM > To: Tomcat Users List > Subject: Re: JMS in a Tomcat Environment > > On Jan 30, 2013, at 11:20 AM, Williams, Nick wrote: > >> Knowing that Tomcat is not a full JavaEE application server, I understand >> that it doesn't support all JavaEE specifications, and that JMS is one of >> the specifications that Tomcat does not implement. However, I'm wondering if >> any Tomcat users out there have any experience with any JMS solutions that >> can be easily integrated into a Tomcat cluster? > > The first one that comes to mind is ActiveMQ... > > https://activemq.apache.org/tomcat.html > > but I'm sure there are other options. Do you have a preferred JMS > implementation? > > Dan > >> >> Thanks, >> >> Nick This e-mail may contain privileged or confidential information. If you are not the intended recipient: (1) you may not disclose, use, distribute, copy or rely upon this message or attachment(s); and (2) please notify the sender by reply e-mail, and then delete this message and its attachment(s). Underwriters Laboratories Inc. and its affiliates disclaim all liability for any errors, omissions, corruption or virus in this message or any attachments. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
