On 1/30/2013 3:27 PM, Jeff Sturm wrote:
-----Original Message-----
From: Williams, Nick [mailto:nicholas.willi...@ul.com]
Sent: Wednesday, January 30, 2013 2:06 PM
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?
I'll toss out my opinion here (noting that I do not speak for Tomcat developers
nor the ASF, nor even my employer I suppose)...
We have an application here that uses JMS, for which we selected HornetQ for a variety of
reasons (e.g. "it's fast"). The app also happens to be hosted on a Tomcat web
application server.
However Tomcat knows nothing of our JMS implementation (with the exception of a
single Java property we set to name our JNDI provider) and HornetQ surely does
not care whether or not it is running within Tomcat. Tomcat is useful to me a
fast and flexible HTTP server that implements some basic specifications (giving
it a degree of interoperability with other webapp containers). With that in
mind, it feels to me as though things like JDBC data sources and JMS
topics/queues are not within the scope of what Tomcat ought to provide, and I
don't wish to see Tomcat become big and bloated in an attempt to be everything
to everyone.
Indeed it seems odd to ask the question on a Tomcat list, unless the goal is to
just solicit opinions on JMS providers from other list members who may have
experience with one or more such provider.
Having been a Java developer since 1.0, and having adopted the language initially for the
beauty of its simplicity, I've watched it transform into an alphabet soup that includes
EJB, JSP, J2EE, etc. None of those specifications provide valuable capabilities I cannot
built into my own application simply by choosing and integrating the right libraries.
Even as an "enterprise" developer it does not feel like the J2EE specification
was written for me, and I find myself wishing that bit of nonsense would just fade into
obscurity, and I would be free to peel back the layers of the various Java technologies
to pick and choose the smallest, simplest components as I see fit.
Anyway, please excuse the rant, and feel free to return to your normal email
list perusal...
-Jeff
Hear, hear.
-Terence Bandoian
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
