Thank you for your guiding explain. You point out there is something great to
me.
Do I understand you right?
I cound use META-INF/sca-contribution.xml at client side
to load the wsdl, instead of place it in the classpath:/wsdl
Mike Edwards <[EMAIL PROTECTED]> wrote: Shaoguang,
Shaoguang,
The SCA specifications allow for the WSDL file to be referenced from a
single location, which can include a remote location, via mechanisms
such as wsdl:location or via the SCA artifact resolution mechanism (see
SCA Assembly spec at www.osoa.org). So copying the WSDL file is not
n
WS consumer will have to put a wsdl file in it class root, the SCADomain load
it automaticly. But this brings a problem if the provider's wsdl changed. So
first I think if the consumer could load the wsdl from
http://[host]:[port]/[servicename]?wsdl,.
There by, when debug the wsdl, the de
