Excellent work. It would probably be a good idea to start getting some of this integrated into CXF itself. Now that a fixes branch for 2.2 has been created and trunk is targeting 2.3, we definitely should start committing some patches for this.
Dan On Wed June 10 2009 4:04:22 am liucong wrote: > Hi all, > > Project Description: > 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. > Any advice or help are welcome! > > Project Information: > 1.Project Status: http://wiki.apache.org/general/soapjms4cxf > 2.Project Code: http://github.com/liucong/jms4cxf2/tree/master > 3.Project JIRA task: https://issues.apache.org/jira/browse/CXF-2253 > > What I have done: > 1.Implement a simple JMS URI > (http://tools.ietf.org/html/draft-merrick-jms-uri-05 ) > 2.Integrate the JMS URI into current jms-transport. It is compatible > with the specification. > 3.Modify the JMS Header Properties and JMS Properties and make it > compatible with the specification. > 4.Modify some code about SOAP fault and MEPs. > > Liu -- Daniel Kulp dk...@apache.org http://www.dankulp.com/blog
