Return-Path: Delivered-To: apmail-cxf-dev-archive@www.apache.org Received: (qmail 71460 invoked from network); 4 Apr 2011 21:33:22 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 4 Apr 2011 21:33:22 -0000 Received: (qmail 70858 invoked by uid 500); 4 Apr 2011 21:33:21 -0000 Delivered-To: apmail-cxf-dev-archive@cxf.apache.org Received: (qmail 70729 invoked by uid 500); 4 Apr 2011 21:33:21 -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 70721 invoked by uid 99); 4 Apr 2011 21:33:21 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Apr 2011 21:33:21 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of eric@tibco.com designates 63.100.100.142 as permitted sender) Received: from [63.100.100.142] (HELO mx1-app.tibco.com) (63.100.100.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Apr 2011 21:33:12 +0000 X-IronPort-AV: E=Sophos;i="4.63,299,1299484800"; d="scan'208";a="22954185" Received: from tibco-5.tibco.com (HELO na-pa-fe02.na.tibco.com) ([63.100.100.5]) by mx1-app.tibco.com with ESMTP; 04 Apr 2011 14:32:51 -0700 Received: from Eric-Johnsons-MacBook-Pro.local ([10.98.39.232]) by na-pa-fe02.na.tibco.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 4 Apr 2011 14:32:50 -0700 Message-ID: <4D9A3901.1010003@tibco.com> Date: Mon, 04 Apr 2011 14:32:49 -0700 From: Eric Johnson User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9 MIME-Version: 1.0 To: dev@cxf.apache.org Subject: Question for CXF developers - level of support for W3C SOAP/JMS specification Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 04 Apr 2011 21:32:50.0804 (UTC) FILETIME=[D96CDB40:01CBF30F] X-TM-AS-Product-Ver: SMEX-10.0.0.1412-6.500.1024-18052.007 X-TM-AS-Result: No--12.702800-8.000000-31 X-TM-AS-User-Approved-Sender: No X-TM-AS-User-Blocked-Sender: No X-Virus-Checked: Checked by ClamAV on apache.org I've a question for the CXF developers. To quickly introduce myself, I'm the chair of the W3C WG for SOAP/JMS [1]. We're at the point where we want to declare a "Proposed Recommendation" (PR) for what is currently our "working draft" [2]. For those unfamiliar, that's the step before declaring something an actual W3C official "Recommendation." [4] To achieve this milestone, we simply need to have two implementations of the specification. More specifically, we need two implementations of each and every normative statement of the specification - even those normative statements that are optional. From work I've done looking at the source code and the samples, it appears that CXF falls into that category. Of particular concern, we're curious about the WSDL extension elements that we've defined, in part because some of the vendors we've talked to have indicated that they will not be supporting such extension elements. In any case, I'm looking for some sort of public statement from the CXF developers about each the normative statements ("assertions") [3] from the spec, and whether each is covered by the CXF implementation. Since the specification has changed slightly since the last working draft - mostly to clarify the assertions, and fix some oversights - it would actually be useful to know about CXF with respect to our latest working copy, and its assertions [5], and that either or both will do. Can anyone comment? Thanks! -Eric Johnson [1] http://www.w3.org/2002/ws/soapjms/ [2] http://www.w3.org/TR/2010/WD-soapjms-20101026/ [3] http://www.w3.org/TR/2010/WD-soapjms-20101026/#assertionsummary [4] http://www.w3.org/2005/10/Process-20051014/tr.html#rec-advance [5] http://dev.w3.org/cvsweb/~checkout~/2008/ws/soapjms/soapjms.html?content-type=text/html;charset=utf-8#assertionsummary