Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
At present we deploy to JBoss 4.2 as this is the application server deployed on our cluster. The application currently only makes use of JBoss’s connection pool handling through JNDI and the JBossWeb’s embedded Tomcat and a couple of JBoss’ Tomcat valves (specifically RewriteValve, nothing too difficult to do ourselves).
JBoss seems like overkill to me, should we switch to straight Tomcat or are there any advantages to staying with JBoss? Does Tomcat integrate any better with Eclipse?
If you aren’t using any of the advanced features of JBoss and you aren’t planning to, then it’s probably better to go with a pure embedded Tomcat. This way, if a security fix is found in Tomcat, you can upgrade just the one single embedded component and move on. JBoss is significantly larger and is thus more difficult to upgrade.
If all you are using from JBoss is JMS or JNDI or something else that is easily embeddable as a separate 3rd party component in Tomcat, then by all means drop JBoss and move to just an embedded Tomcat.
When should you stick with JBoss? When using JBoss makes your life so much easier that the extra work of upgrading JBoss is worth the effort. This is true for many people. It sounds like it is not true in your case.
As far as integrating better with Eclipse, I expect that both integrate pretty well with Eclipse. I use MyEclipse, which supports both JBoss and Tomcat. So this may depend on what version of Eclipse and what plugins you are using.