Return-Path: X-Original-To: apmail-camel-users-archive@www.apache.org Delivered-To: apmail-camel-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7C4417041 for ; Tue, 26 Jul 2011 02:26:17 +0000 (UTC) Received: (qmail 26452 invoked by uid 500); 26 Jul 2011 02:26:17 -0000 Delivered-To: apmail-camel-users-archive@camel.apache.org Received: (qmail 26300 invoked by uid 500); 26 Jul 2011 02:26:16 -0000 Mailing-List: contact users-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@camel.apache.org Delivered-To: mailing list users@camel.apache.org Received: (qmail 26292 invoked by uid 99); 26 Jul 2011 02:26:16 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Jul 2011 02:26:16 +0000 X-ASF-Spam-Status: No, hits=0.6 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of willem.jiang@gmail.com designates 209.85.210.49 as permitted sender) Received: from [209.85.210.49] (HELO mail-pz0-f49.google.com) (209.85.210.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Jul 2011 02:26:09 +0000 Received: by pzk33 with SMTP id 33so9927847pzk.36 for ; Mon, 25 Jul 2011 19:25:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=Gy7DymXxDkv0LtKNoNKAVm3AQaljyn5AEuHiJOuV0Vs=; b=vCx8QY8/YpBAD+uVsYAeb8ub3yJHEUJPhxoBuLrXQRugZtsM8v+6vc/pyC7Vyr0Hbu npmE0LS+fJnJnt9wE2Xhy7Hx3aV8nP4oZVim/A7AuTYhvN+sK+PZuapYOr1qUH7+oXfE k1SsEIVdkAPINHpm0mCftSKnhzInShM91BC0Q= Received: by 10.68.35.70 with SMTP id f6mr8569826pbj.506.1311647147593; Mon, 25 Jul 2011 19:25:47 -0700 (PDT) Received: from [192.168.0.158] ([123.116.34.210]) by mx.google.com with ESMTPS id l7sm11719pbh.90.2011.07.25.19.25.45 (version=SSLv3 cipher=OTHER); Mon, 25 Jul 2011 19:25:46 -0700 (PDT) Message-ID: <4E2E25A7.2060202@gmail.com> Date: Tue, 26 Jul 2011 10:25:43 +0800 From: Willem Jiang User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:5.0) Gecko/20110624 Thunderbird/5.0 MIME-Version: 1.0 To: users@camel.apache.org Subject: Re: CxfEndpoint data formats References: <1311610720614-4631394.post@n5.nabble.com> In-Reply-To: <1311610720614-4631394.post@n5.nabble.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org On 7/26/11 12:18 AM, Jens wrote: > Hi, > > is there any way to use different data formats for sending and receiving > messages with a given CXF endpoint? > > E.g. if I have a route like > > from("queue:...").to(cxf:...).process(...) > > I'd like to provide the message for the CXF endpoint in PAYLOAD format but > get the response from the service call as a POJO for further processing. If you can extract the request message from the PAYLOAD, you can send the POJO request from the cxf endpoint. > > Alternately, is there an easy way to have PAYLOAD format return valid > (wrapped) XML documents? Unfortunately, the unwrapping that PAYLOAD format > performs (and expects for incoming data) on the message makes it hard to use > standard XML features like XPath or XSLT to process PAYLOAD messages. I don't quit understand you question, but can you try to set this wrappedStyle option to be true to see if anything changed. Here is the description of the wrappedStyle "New in 2.5.0 The WSDL style that describes how parameters are represented in the SOAP body. If the value is false, CXF will chose the document-literal unwrapped style, If the value is true, CXF will chose the document-literal wrapped style" > > Thanks, > Jens > > -- > View this message in context: http://camel.465427.n5.nabble.com/CxfEndpoint-data-formats-tp4631394p4631394.html > Sent from the Camel - Users mailing list archive at Nabble.com. > -- Willem ---------------------------------- FuseSource Web: http://www.fusesource.com Blog: http://willemjiang.blogspot.com (English) http://jnn.javaeye.com (Chinese) Twitter: willemjiang Weibo: willemjiang