Return-Path: Delivered-To: apmail-cxf-dev-archive@www.apache.org Received: (qmail 42018 invoked from network); 10 Jun 2009 08:05:16 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 10 Jun 2009 08:05:16 -0000 Received: (qmail 84021 invoked by uid 500); 10 Jun 2009 08:05:28 -0000 Delivered-To: apmail-cxf-dev-archive@cxf.apache.org Received: (qmail 83976 invoked by uid 500); 10 Jun 2009 08:05:27 -0000 Mailing-List: contact dev-help@cxf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cxf.apache.org Delivered-To: mailing list dev@cxf.apache.org Received: (qmail 83966 invoked by uid 99); 10 Jun 2009 08:05:27 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Jun 2009 08:05:27 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of liucong07@gmail.com designates 209.85.216.197 as permitted sender) Received: from [209.85.216.197] (HELO mail-px0-f197.google.com) (209.85.216.197) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Jun 2009 08:05:16 +0000 Received: by pxi35 with SMTP id 35so39318pxi.24 for ; Wed, 10 Jun 2009 01:04:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:content-type :content-transfer-encoding; bh=JWLpUnDNeLYL3zzghM3xMSj+UfRe4D2FQEr9iVg42xw=; b=dPYmCX3qDuHLvwcnGLkw6p8EOiG4M49rEDV92HdPrxMOXD5txZ+f4zsXm7guiAcrl1 X8OR8/QVMhmC3OLYmuFc0B+F5xSH+WK4Z8R/debMyF0hSobsgxydAcs6km51uNHs7p9k DUIDBduGpRhBDHm8km+/JO8Tb2WD+qRKkUYhU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; b=GcyaX9ysVhJEvtPhH8l7Fs5NSD6qnw4Yru5+IuE3YT24MJwQZwhID77QpoDiNrIfQs BW6setvZMn0Bc8dF+AV0Ha2tmFjJ3evdf5B15iYO5M2axQGgBj3QBf71dT6CKoErNDOk IXhk99NvgqOsfN2vdJXCTygd+WeitdzWOSKms= Received: by 10.115.23.19 with SMTP id a19mr1679615waj.174.1244621096338; Wed, 10 Jun 2009 01:04:56 -0700 (PDT) Received: from ?133.133.133.57? ([124.16.137.194]) by mx.google.com with ESMTPS id m30sm8519956wag.18.2009.06.10.01.04.53 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 10 Jun 2009 01:04:55 -0700 (PDT) Message-ID: <4A2F6906.7090200@gmail.com> Date: Wed, 10 Jun 2009 16:04:22 +0800 From: liucong User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: dev@cxf.apache.org, Willem Jiang Subject: SOAP/JMS specification for CXF [Project Status] Content-Type: text/plain; charset=GB2312 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org 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