Update Report on upcoming JSLEE Specification 1.1
September 5 2007,
The JSLEE (JAIN SLEE) specification is under continuous development to refine the standard for next generation network application platforms. JSLEE version 1.1 – the first revision of the JSLEE specification – is currently in review stages and reached Proposed Final Draft in August 2007.
what is the process behind the JSLEE Standard?
Similar to other Java Community Process specifications, the JSLEE standard involves the use of Java Specification Request (JSR) documents that describe proposed specifications and technologies to be added to the Java platform. Formal public reviews of JSRs are conducted before the JSR becomes final and are voted on by the JCP Executive Committee. A final JSR provides a reference implementation (RI), which demonstrates the specification can be implemented, and a Technology Compatibility Kit (TCK), which is used to verify the compliance of any implementation claiming compliance to the latest specification.
which organisations are involved in the process?
Expert Group:
| AePONA | Armstrong, Charles | Bea Systems |
| Cingular Wireless | Instituto de Telecomunicacoes |
Ivov, Emil |
| jNetX Inc. | Kapsch Carriercom | Lucent Technologies |
| Mobilkom Austria AG & Co KG |
Net4Call A.S | NIST |
| Nokia Corporation | Nortel | NTT Data Corporation |
| O'Neill, Brian | OpenCloud Ltd | Personeta, Inc. |
| Red Hat Middleware LLC | Sun Microsystems, Inc. | Telecom Italia |
| TrueTel Communications Inc. |
Vodafone Services Group Limited |
David Ferry of OpenCloud Ltd is the specification lead.
what is the status of the JSLEE 1.1 specification?
JSLEE 1.1 (JSR 240) reached public review in February 2007. A small number of comments that required changes were received by the expert group and the specification reached Proposed Final Draft on 24 August 2007. The Reference Implementation (RI) and Technology Compatibility Kit (TCK) are being prepared for Final Release.
The group is confident that the JSR 240 (JSLEE 1.1) specification will reach Final Release status in 2007.
(JSLEE 1.0 achieved Final Release status in March 2004.)when will JSLEE 1.1-compliant platforms be available on the market?
Vendors can claim JSLEE 1.1 compliance after the Final Release of JSR 240 is made available and once the vendor’s platform has successfully completed the compliance testing process. This involves downloading and testing against the TCK and publication of the results. It is not possible, for example, to claim compliance with the JSLEE 1.1 'public review' specification as there is no TCK associated with the public review that could be used to validate this claim.
why was a new release of the JSLEE standard required?
The primary focus of the updated JSLEE 1.1 standard is the Resource Adapter (RA) architecture. The goal of the RA architecture is to allow Resource Adaptor implementations that use and fulfill contracts defined in the JSLEE 1.1 specification to be deployed and run in any compliant JSLEE.
why is compliance important?
One of the key aims behind Java standards is to achieve binary portability of applications across compliant platforms. The importance of compliance is amplified with the appearance of a new release of the standard, and new products to support it. Therefore, backwards compatibility between JSLEE 1.0 and JSLEE 1.1 is a key priority for the JSLEE 1.1 expert group to ensure that applications written for a 1.0- compliant platform will run unaltered when the platform is upgraded to a 1.1- compliant version. JSLEE 1.0 applications will run unaltered on JSLEE 1.1 containers, provided no proprietary APIs, libraries or features of a particular vendor platform have been used by the application.
why is the use of JSLEE growing?
JSLEE is increasingly being accepted by carriers, network equipment vendors and IT developers as the ideal basis for next generation network infrastructure software. The main strengths of JSLEE over alternative approaches, and which are driving market adoption are the openness, richness and completeness of the programming model; interoperability with fixed, mobile and IP networks; the portability of services; the asynchronous programming model; and support for resilience.
To view the Proposed Final Draft of JSLEE Version 1.1 go to: www.jcp.org
###
Notes to editor:
About OpenCloud
OpenCloud was formed in New Zealand in 2000 to create open standard software that would revolutionise the portability and interoperability of services in telecommunications, specifically in the evolution to IP and 3G IMS. The company was founded on the vision that the use of Java within the telecommunications network would stimulate innovation, interoperability and simplicity in telecommunication infrastructure equipment. In autumn this year, OpenCloud won global consulting firm Frost & Sullivan’s Product Differentiation Innovation of the Year award in the European telecommunications market.
OpenCloud works with partners to deliver, integrate and support end-to-end solutions incorporating OpenCloud products to global network operators and service providers. OpenCloud has representatives in: Cambridge, UK; Wellington, New Zealand; Madrid; Tokyo; and San Francisco. More information is available at www.opencloud.com.
Media Contact:
Liz Dey/Bettina Winters
Hotwire PR
opencloud@hotwirepr.com
+44 (0)207 608 2500