SOAP/JMS specification for CXF

Outline


Project Description

Apache CXF is an open source services framework. CXF helps you build and develop services using frontend programming APIs, like JAX-WS. These services can speak a variety of protocols such as SOAP, XML/HTTP, Restful HTTP, or CORBA and work over a variety of transports such as HTTP, JMS or JBI.

SOAP over JMS offers an alternative messaging mechanism to SOAP over HTTP. SOAP over JMS offers more reliable and scalable messaging support than SOAP over HTTP.

SOAP over JMS specification(http://www.w3.org/TR/soapjms/) is aimed at a set of standards for the transport of SOAP messages over JMS (Java Message Service). The main purpose is to ensure interoperability between the implementations of different Web services vendors.

CXF does support SOAP over JMS, but it does not meet the current draft specification defined at http://www.w3.org/TR/soapjms/ and instead uses some proprietary formats, headers, url formats, etc. This project would update the SOAP/JMS support in CXF to be completely specification compliant.

Upon sucessful completion of the SOAP/JMS project, CXF will become one of the very first Open Source implementations of the SOAP/JMS specificiation.

The main concerns are as follows:


Project Timeline

First Week(5.20-5.26)

I have known the configuration of JMS address for current implementation. I’ll investigate the JMS URI, and get some code from Camel project for JMS URI and test it.

Second Week(5.27-6.2)

I’ll use the Camel JMS URI to implement the JMS URI for SOAP/JMS. And do some tests to make sure the JMS URI works.

Third Week(6.3-6.9)

I’ll integrate the JMS URI with the current implementation of SOAP/JMS. The JMS URI configuration information will replace the jms:address of current implementation.

4th Week(6.10-6-16)

I’ll modify the JMS Message Header properties and JMS message properties to make them conformance with the specification.

5th Week(6.17-6.23)

I’ll modify the MEPs to make them conformance with the specification.

6th Week(6.24-6.30)

I’ll make a checkpoint with my mentor and submit midterm evaluations.

7th Week(7.1-7.7)

I’ll work on the WSDL extension for WSDL usage and make the WSDL definition conformance with the specification.

8th Week(7.8-7.14)

I’ll still work on the WSDL extension for WSDL usage and make the overriding rule work.

9th Week(7.15-7.21)

I’ll work on the SOAP Fault for SOAP/JMS and make it conformance with the specification.

10th Week(7.22-7.28)

I’ll work on the test suite (http://dev.w3.org/2008/ws/soapjms/testcases/) . I’ll write an integration test for SOAP over JMS. Then I will update the documents for SOAP/JMS in CXF.

11-12th Week(7.29-8.12)

I’ll still work on the test suite to make the implementation pass the tests as possible as I can.

Final Week(8.13-8.19)

I will finish all the tests and refinement with my mentor.


Project Status

First Week(5.20-5.26)

Second Week(5.27-6.2)

Third Week(6.3-6.9)

4th Week(6.10-6.16)

5th Week(6.17-6.23)

6th Week(6.24-6.30)

7th Week(7.1-7.7)

8th Week(7.8-7.14)

9th Week(7.15-7.21)

10th Week(7.22-7.28)

11th Week(7.29-8.5)

12th Week(8.6-8.12)

13th Week(8.13-8.19)


Source Code


Project Tasks


soapjms4cxf (last edited 2009-09-20 23:35:25 by localhost)