- Difference between glassfish and tomcat upgrade#
- Difference between glassfish and tomcat software#
- Difference between glassfish and tomcat download#
So your using C3P0 and the first thing that comes to mind is, "may the force be with you"! Seriously, aside from connection pooling, statement pooling, data persistence, object caching, data relations, data mapping or database abstraction and other Java EE5 aspects, have bearing on the comparison of an E.J.B server (Glassfish), with the open source servlet / web container Tomcat? Pardon my duh but either I've missed the point or we got so left field, we might just compare peanuts with cashews, resolve these last two statements as nuts. His other interests are music, psychology, languages, the proper use of semicolons, and finding good food.Ĭomment posted by: GlassCat, 14 years ago He has no fixed address and has left footprints on 40-something different countries around the world. Roger Keays is an artist, an engineer, and a student of life. Tomcat might be old and boring, but it is fast, stable and doesn't have buggy features.
Difference between glassfish and tomcat upgrade#
After trying to upgrade several times to Glassfish we just keep hitting stopper bugs that make me wonder if anybody actually uses it for anything more than "Hello World" applications. Referencesįive and half years later and Tomcat is still our server of choice. Glassfish looks great, but the problems above are show stopper for us, so we have to stay with Tomcat unless I come up with a way to do these things in Glassfish. Additionally, it appears that instances of webapps in Glassfish can't be individually configured by setting environment variables in the config file (the section is practically empty) and they cannot be mapped to the same context path even if they are deployed to different hosts. This is why you can't have a single deployment directory or jailed manager per virtual host. In Glassfish, webapps don't live in a single virtual host, they are mapped to one or more virtual hosts. The main problem with Glassfish is that its virtual hosting features don't meet our requirements. Tomcat requires an additional containers Įach host can listen on an arbitrary combination of portsįor Tomcat, a host in one cannot share ports with a host in another Possible in Tomcat's context.xml or server.xmlĮach host has their own authentication realm
Difference between glassfish and tomcat software#
Well, what better way to decide about an upgrade than to build a comparison matrix? Lets have a look then - a comparison to Tomcat is all I'm really interested in here, although one of the key features of our software is its multisites capability, so support for virtual hosting is especially important. Needless to say, I'd be quite happy to upgrade. Then there's the other advantages of Java EE 5.0 like dependency injection, transaction management and hooks for automatic Entity enhancement.
Difference between glassfish and tomcat download#
We're now deploying JPA 1.0, JSF 1.2, EL 1.0, JSTL, Mail and Activation jars which account for over 65% of the download size and are all included in a Java EE 5.0 server. The stack we're using now to build applications for Sunburnt SEO is so close to being a complete Java EE 5.0 environment that I've been giving some thought to dumping support for the old Servlet 2.4 environment altogether.