GlassFish 3.1 >= GlassFish 2.x + GlassFish 3.0
By arungupta on Dec 16, 2010
GlassFish v1 was about Java EE 5 compliance (single instance), v2 allowed such applications to be deployed in multi-instance cluster with seamless session failover and high availability, GlassFish 3 focused on Java EE 6 compliance, 3.1's focus is deploying Java EE 6 in multi-intance cluster.
One way to show this using a simple equation is ...
GlassFish 3.1 = GlassFish 2.x + GlassFish 3.0
However GlassFish 3.1 added a whole lot of new functionality which was not in any of the earlier versions and is listed below:
Clustering and High Availability
- Shoal GMS over Grizzly implementation
- Consistent hash based session replication
- Preferred fail-over by load-balancer plugin
- Metro HA: Reliable messaging sequence failover, Secure conversation session failover
- Support for conventional clustering of MQ brokers in embedded mode
- Improved automatic delegated transaction recovery with shared file system
- Improved embedded API support
- Updated NetBeans and Eclipse plugin
- GlassFish Hudson Plugin
Management and Monitoring
- Application versioning support
- Application scoped resources
- Statement leak detection and reclaim
- Custom validation template for JDBC con. pool
- Support for PAM realm
- Certificate realm extension
- SSH based remote management and provisioning
- Console based on RESTful API
- WS-I compliance: BP 1.2/2.0, BSP, 1.1, RSP 1.0
- Grizzly WebSocket support
- Improved CDI, JSON, hypermedia support in Jersey
- Technology refresh – JSF 2.1, Servlet 3.0 MR, CDI, Grizzly, OSGi, JPA, Jersey, Bean Validation, Metro, UC, etc.
- Implementation of various Enterprise OSGi Specs
So that's why GlassFish 3.1 >= GlassFish 2.x + GlassFish 3.0!