We have some basic parsing code for WSDL service contracts right now
but this needs to be finished. To put a stake in the ground I intend
to make the following work:
* support for parsing <interface.wsdl> elements
* support for WSDL resolution based on the WSDL2.0 wsdlLocation
mechanism. This will require the user to specify the location of the
WSDL on each usage.
An example would be:
<service name="foo">
<interface.wsdl interface="http://example.com#wsdl.interface
(FooService)"
wsdlLocation="http://example.com wsdl/
example.wsdl"/>
...
Relative location URIs will be resolved against the classpath for
the composite.
* To start with, I don't plan to cache WSDLs instances - we can
optimize performance when necessary
There are no dependencies on WSDL in the core so I plan to move all
the WSDL processing to an extension module idl/wsdl. I will modify
any bindings that specifically need WSDL (which I hope is just the
webservice ones) to depend on this extension. I don't plan to do
anything else at this time with bindings that use WSDL information -
once the interface stuff is working we can take another look.
--
Jeremy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
