The Source for Java Technology Collaboration
User: Password:
Register | Login help    

Search

Online Books:
java.net on MarkMail:


Binod

Binod P.G is a senior staff engineer in the Java Web Services division at Sun Microsystems. He is an architect in the Application Server development team and is working on Project SailFin. He is also a co-specification lead of the Java EE Connector Architecture 1.6 Expert Group and a member of JDBC 4.0 expert group. In the past, he was involved in the development of many areas of the glassfish applicaton server, including Java EE Service Engine, Server Startup, Connector 1.5, JDBC, Connection Pool and JMS provider integration. He is also one of the owners of Generic Resource Adapter for JMS project. Prior to joining Sun in 2000, he has worked on a number of server side software technologies including IMS PL/1 programs in IBM Mainframes and internet projects in Microsoft IIS.

 

Binod's blog

V3, Java EE 6 and SIP Servlets

Posted by binod on December 10, 2009 at 8:24 AM PST

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.

  1. Doing a modularized OSGI based SIP Servlet Container and SailFin CAFE is probably the most obvious item
  2. 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.
  3. 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.
  4. 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
  5. 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
  6. 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 (users@sailfin.dev.java.net).

Comments
Comments are listed in date ascending order (oldest first)
Syndicate content