Besides EAR and EJB, what do I get from a J2EE app server that I don't get in a servlet container li
        Posted  
        
            by dacracot
        on Stack Overflow
        
        See other posts from Stack Overflow
        
            or by dacracot
        
        
        
        Published on 2008-11-06T15:45:16Z
        Indexed on 
            2010/05/16
            21:00 UTC
        
        
        Read the original article
        Hit count: 353
        
We use Tomcat to host our WAR based applications. We are servlet container compliant J2EE applications with the exception of org.apache.catalina.authenticator.SingleSignOn.
We are being asked to move to a commercial J2EE application server.
- The first downside to changing that I see is the cost. No matter what the charges for the application server, Tomcat is free.
 - Second is the complexity. We don't use either EJB nor EAR features (of course not, we can't), and have not missed them.
 
What then are the benefits I'm not seeing?
What are the drawbacks that I haven't mentioned?
Mentioned were...
- JTA - Java Transaction API - We control transaction via database stored procedures.
 - JPA - Java Persistence API - We use JDBC and again stored procedures to persist.
 - JMS - Java Message Service - We use XML over HTTP for messaging.
 
This is good, please more!
© Stack Overflow or respective owner