Hi all,
I have checked into the CXF-BC trunk and in fact the WSDL proxy is
already defined in the consumer mode.
I can see a retrieveWSDL() method that, if the wsdl resource is null,
get the WSDL of the target server/endpoint. This method is called in the
validate() one when the endpoint definition is null.
So it seems that the component documentation is not up to date as it's
written that the WSDL attribute is required.
I make a test and update the wiki page if required.
Regards
JB
Jean-Baptiste Onofré wrote:
Hi gentlemen,
In servicemix-http 2009.01 component, we made an enhancement to be able
to get the WSDL provided by the targetService/targetEndpoint using a
consumer HTTP endpoint. If the user doesn't provide any WSDL, the
component can get the target one from the endpoint description, add
binding if required and expose it.
This behavior is not present in the HTTP component used in provider
mode. Used as provider, the HTTP component requires a WSDL provided by
the user. I haven't yet test if we can define a URL as WSDL Resource for
provider (for example, using
http://targethost:targetport/targetcontext/target.wsdl).
Moreover, CXF-BC requires a provided WSDL (both used in provider or
consumer). It doesn't support the kind of WSDL proxy as made in HTTP.
I propose to:
1/ make a test of a HTTP WSDL Resource in the HTTP and CXF-BC component
used as provider.
2/ add WSDL proxy support in the CXF-BC component (when used as
consumer) as made in the HTTP component.
Does it make sense for you ?
Thanks for your feedback,
Regards
JB
--
Jean-Baptiste Onofré
---------------------------------
HomePage
http://www.nanthrax.net
---------------------------------
Contacts
[email protected]
[email protected]
---------------------------------
OpenSource
BuildProcess/AutoDeploy
http://buildprocess.sourceforge.net
Apache ServiceMix
http://servicemix.apache.org
-----------------------------------
PGP : 17D4F086
