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 81C9CEC65 for ; Sat, 26 Jan 2013 07:38:15 +0000 (UTC) Received: (qmail 39087 invoked by uid 500); 26 Jan 2013 07:38:14 -0000 Delivered-To: apmail-camel-users-archive@camel.apache.org Received: (qmail 39034 invoked by uid 500); 26 Jan 2013 07:38:14 -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 39019 invoked by uid 99); 26 Jan 2013 07:38:13 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 26 Jan 2013 07:38:13 +0000 X-ASF-Spam-Status: No, hits=2.0 required=5.0 tests=SPF_NEUTRAL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: 216.139.236.26 is neither permitted nor denied by domain of sreeraaman@gmail.com) Received: from [216.139.236.26] (HELO sam.nabble.com) (216.139.236.26) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 26 Jan 2013 07:38:08 +0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1Tz0Kh-0004X9-3u for users@camel.apache.org; Fri, 25 Jan 2013 23:37:47 -0800 Date: Fri, 25 Jan 2013 23:37:47 -0800 (PST) From: Sriraman Gopalan To: users@camel.apache.org Message-ID: <1359185867109-5726313.post@n5.nabble.com> Subject: Camel CXF component - Adding custom context classes via the uri options MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Dear All, We use the camel - cxf component to invoke external web services. We use the uri format with options to set various attributes as shown below: cxf://?serviceName=&portName=&wsdlURL=&defaultOperationName=&serviceClass= This works well for most cases without any issues. However, the issue is with one of the web services wherein for one operation's response , one of the element's type is marked as xsd:any which resulted in the generated classes having Object as the attribute type. wsdl snippet: Generated Java Code Snippet: public static class GetWTDataResult { @XmlAnyElement(lax = true) protected Object any; public Object getAny() { return any; } public void setAny(Object value) { this.any = value; } } While invoking the actual service ( a .NET web service), the response comes with the xsd and the data. Actual web service response snippet: Equity 6626 14947.77 2013-01-25T15:52:00+05:30 To make jaxb aware of this element "NewDataSet", we generated the jaxb classes from the xsd in the web service response as shown above using maven-jaxb2-plugin. Now, the issue is how do we make this custom jaxb classes available to cxf so that it correctly deserializes the response? After searching the net, we found that this can be accomplished via code as shown in the following link: progress documentation Since, we are using camel cxf component, is there any other way to indicate to cxfendpoint to use these extra jaxb classes? I did notice that the camel cxf component allows setting of custom cxf properties via the properties.XXX format. However, I am not too sure how to set this for the jaxb.additionalContextClasses property which is a property in the jaxwsproxyfactory bean. Any help would be highly appreciated. best regards Sriraman. -- View this message in context: http://camel.465427.n5.nabble.com/Camel-CXF-component-Adding-custom-context-classes-via-the-uri-options-tp5726313.html Sent from the Camel - Users mailing list archive at Nabble.com.