You're right, binding.ws does currently require a wsdl be provided, this
is something we hope to fix in the next release -
http://cwiki.apache.org/confluence/display/TUSCANYWIKI/SCA+Java+Next+Release+Contents
If the url do provide wsdl and the url of your web service is turning out to
be some
Thank you for your attention ant!
You encouraged me reading osoa's specification again, then I found your point.
OK, now let me speak about my question to some further:
I found in WebService_Binding 2.3, wsdl should be generated for an binding.ws,
and
there follows a generation rule in the
On 7/18/07, shaoguang geng [EMAIL PROTECTED] wrote:
When I work on the svn code, I found that the service address of a
binding.ws depends on it's uri attribute, not the soap:address inside
the wsdl file. If the soap:address is some thing different from the
binding.ws's uri, or it does not
When I work on the svn code, I found that the service address of a binding.ws
depends on it's uri attribute, not the soap:address inside the wsdl file. If
the soap:address is some thing different from the binding.ws's uri, or it
does not exists absolutely, the client will get a confusion form