Resin Documentationapp server |
resin 4.0.2 release notes
The focus of Resin 4.0.2 development was the following:
Resin 4.0.x is the active development branch. Resin 4.0.2 continues work on the Servlet 3.0 draft specification as an early access release. The Java Injection specification has changed significantly between 4.0.1 and 4.0.2. Resin now supports the JSR-330 annotations for Java Injection. The main changes are repackaging and renaming of the key injection annotations to match JSR-299. The Java Injection Tutorial has been updated for the new injections. Resin's clustering now includes support for clustered queues and topics. The primary clustered queue is a singleton queue with failover. The clustered topics notify all servers in a cluster pod. We've added /resin-admin features to improve visibility to the server, development and debugging, and adminstration. The "summary" tab now includes statistical gathered as the server is running including request counts, request times, CPU time, netstat reports, and database activity. A "postmortem" tab helps debugging of a server crash by displaying the server state at the time just before a restart. Customized statistics gathering based on JMX is now available through the <jmx> and <jmx-delta> tags of the <resin:StatManager> service. Customizable REST pages are now available through /resin-admin using PHP to script the gathered data. The REST capability is intended for integration with administration tools like Nagios. Distributed deployment has been enhanced with staging and versioning capabilities, and integrated with the development flow with ant and maven tasks. A new application version can be deployed with the following process:
Quercus development in 4.0.2 has focused on bugs fixes and QA regression cleanup. Resin 4.0.2 now includes support for the HTML 5 WebSocket protocol, which is a fully-bidirectional TCP connection established using HTTP handshaking, allowing for true interactive applications with HTML 5 browsers. On top of WebSockets, we've created JMTP and HMTP as a programmable messaging layer. JMTP (JSON Message Transport Prototocol) and HMTP (Hessian Message Transport Protocol) provide general messaging, RPC, and publish/subscribe capabilities in a clean, simple interface.
|