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
necessary.
However, for a Java developer, there is usually the need to derive a
Java interface from the WSDL in order to write the Java code for that
interface. It is always possible then, that the Java interface gets out
of sync with the WSDL file. There is no easy way around this, but the
SCA runtime can at least check for compatibility and raise a fault if
they do not match.
Yours, Mike.
shaoguang geng wrote:
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 developer will have to edit on the two side.
Would anyone think this a better idea?
---------------------------------
Building a website is a piece of cake.
Yahoo! Small Business gives you all the tools to get online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
