Jeff Tulley wrote:
Last I checked (a while ago, admittedly), JBoss was architected such that you can deploy only the pieces you need - VERY modular. So, you can make it not a "monster", but rather just Tomcat + JTA, if I am not mistaken. It seemed at the time (early JBoss 3.0 days) that such a thing was not that hard either.
That's the idea, and it didn't change with JBoss 3.2.x. I think it would have been a terrible idea to change this ;-)
As a reminder, I work for Jboss Group. My goal is to:
- be more responsive, and sync as fast as possible JBoss with Tomcat
- improve the quality of the Tomcat integration (in progress)
- offer a seamless upgrade path from Tomcat standalone should some J2EE features become needed
Cool.
Along the lines of the original thread -- I believe it is truly a shame that one must generally drag in an entire app server in order to get JTA / transaction management support. [Sheesh -- you'd think you needed an entire app server to do anything from the current state of affairs, when the reality is that Tomcat is all you need for a lot of things.]
I understand JBoss is architected to be modular, separable, etc. It would be great if someone could go one step further and produce a seamlessly Tomcat pluggable, JTA-only sub-distribution of JBoss -- or just an Ant script to produce that from a normal JBoss distro or CVS label.
-- Jess Holle
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
