Return-Path: Delivered-To: apmail-camel-dev-archive@www.apache.org Received: (qmail 88323 invoked from network); 11 Mar 2011 14:19:24 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 11 Mar 2011 14:19:24 -0000 Received: (qmail 47084 invoked by uid 500); 11 Mar 2011 14:19:23 -0000 Delivered-To: apmail-camel-dev-archive@camel.apache.org Received: (qmail 47048 invoked by uid 500); 11 Mar 2011 14:19:23 -0000 Mailing-List: contact dev-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@camel.apache.org Delivered-To: mailing list dev@camel.apache.org Received: (qmail 47040 invoked by uid 99); 11 Mar 2011 14:19:23 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 Mar 2011 14:19:23 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 Mar 2011 14:19:21 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 7645D3A3046 for ; Fri, 11 Mar 2011 14:18:59 +0000 (UTC) Date: Fri, 11 Mar 2011 14:18:59 +0000 (UTC) From: "William Tam (JIRA)" To: dev@camel.apache.org Message-ID: <1573495237.13416.1299853139481.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <420208991.11334.1299780060293.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] Assigned: (CAMEL-3778) Support CXF Dispatch mode at CXF Endpoints MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/CAMEL-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Tam reassigned CAMEL-3778: ---------------------------------- Assignee: William Tam > Support CXF Dispatch mode at CXF Endpoints > ------------------------------------------ > > Key: CAMEL-3778 > URL: https://issues.apache.org/jira/browse/CAMEL-3778 > Project: Camel > Issue Type: New Feature > Components: camel-cxf > Affects Versions: 2.6.0 > Reporter: Aki Yoshida > Assignee: William Tam > Fix For: 2.7.0 > > Attachments: patch-20110310.txt, tests.zip > > > Hi, > Sometime ago I asked in this mailing list whether it is possible to use the dispatch mode of CXF in the Camel's CXF endpoint. The answer was no. But I wanted to have the CXF dispatch mode so that I can run SOAP intermediary/gateway scenarios with CXF features enabled and send arbitrary SOAP messages from a single endpoint. > Now I have implemented this feature and I would like to hear what you think. > In short, I modified CxfSpringEndpoint and CxfEndpoint so that Camel uses the CXF dispatch mode when no service class nor WSDL is specified in the endpoint configuration. For example, you can configure the endpoint as: > {code:xml} > address="http://localhost:9000/SoapContext/GreeterPort" > endpointName="s:GreeterPort" > serviceName="s:GreeterService" > bus="#bus"> > > > > > {code} > In this case, the endpoint is set up for the dispatch mode. The dispatch mode supports two operations Invoke and InvokeOneWay and the default operation is Invoke. You can change the operation by simply setting the camel header operationName. > I added two unit tests classes to show how the dispatch mode works for both PAYLOAD and MESSAGE data format. > I am attached all the file to this ticket. I would appreciate if you can comment on this feature. > Thanks. > Regards, Aki -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira