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
Rémy
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
