axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 17303] - Invalid WSDL generated when using wrapped/literal
Date Thu, 06 Mar 2003 22:07:20 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17303>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17303

Invalid WSDL generated when using wrapped/literal





------- Additional Comments From rkellogg@micros.com  2003-03-06 22:07 -------
This recent attachment(03/06/03) demonstrates import problems with Visual 
Studio.NET 2003.

Basically, I have a web service that takes 2 strings and returns a string.

Three WSDD files are attached.  They vary in how the service is encoded:

  <service name="Echo2StringsDocumentLiteralService" style="document" 
use="literal"> - FAILS 
  <service name="Echo2StringsRPCLiteralService" style="rpc" use="literal"> - 
FAILS
  <service name="Echo2StringsWrappedService" style="wrapped"> - WORKS

The generated WSDL from each deployment is included.  It is my assumption, that 
I could have specified provider="java:RPC" and received the same results.

All documents that I read, suggest you should always use document/literal 
encoding for .NET.

Mime
View raw message