Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Message-ID: <4E97EDD6.7000906@die-schneider.net>
Date: Fri, 14 Oct 2011 10:07:50 +0200
From: Christian Schneider <chris@die-schneider.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: users@camel.apache.org
Subject: Re: Camel SOAP
References: <1318536526229-4900457.post@n5.nabble.com>
In-Reply-To: <1318536526229-4900457.post@n5.nabble.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi Kobe,

that is not possible at the moment. The SOAP Dataformat works with the 
annotated classes. So the wsdl alone does not work.

If you have the use case that is implemented by the google code 
camel-soap you can simply use this implementation.
Of course we may still consider implementing this if there is enough 
demand from users.

The problem with this aproach is in my opinion that it is very limited. 
It only allows to map simple types to a methed with these parameters. 
That is not how most web services work.
Especially the document oriented webservices work with exactly one 
"document" that is a complex type. This is not possible with the google 
code implementation.


Christian


Am 13.10.2011 22:08, schrieb Kobe:
> Does Camel SOAP allow me to connect to a SOAP web service using its WSDL
> alone
> as implemented by
>
>    http://code.google.com/p/camel-soap/wiki/Introduction
>
>
> thnk
>
> /Kobe
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/Camel-SOAP-tp4900457p4900457.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>

-- 
Christian Schneider
http://www.liquid-reality.de

Open Source Architect
http://www.talend.com