V3, Java EE 6 and SIP Servlets
Much awaited GlassFish V3 is released today. The modular, OSGI based Java EE 6 product has been making headlines for some time now. I have been experimenting V3 for some time now, basically from the POV of SailFin and SIP Servlets. Here are some items on top of mind that are relevant for SIP Servlets and next SailFin release.
- Doing a modularized OSGI based SIP Servlet Container and SailFin CAFE is probably the most obvious item
- Java EE 6 has standardized module names and application names. That will be applicable for SIP Servlets, especially since application composition in SIP Servlets is based on SIP module names.
- The new JNDI namespaces introduced in Java EE 6, especially the module name is quite applicable for SIP Servlets. The current SIPFactory and SIPSessionsUtil lookup should benefit from the newly introduced namespaces (global, module,app) etc along with namespaces. Take a look at Java EE 6 specification (chapter EE5.2.2) for more details.
- The servlet extensibility introduced in the latest servlet specification is certainly applicable for SIP Servlets also, especially since Converged Application Frameworks are on the rise
- Asynchronous servlets and EJBs would help converged application development, since communication protocols are much more asynchronous than the Java EE technologies and hence it will be a good mechanism for integrating communication with
- CDI (JSR 299) is certainly important for SIP Servlets as well. Looking forward to using it for SailFin CAFE
Are there any thing else, you would like to see in SailFin v3? Do send e-mails to sailfin mailing lists (email@example.com).