Return-Path: 
 <axis-dev-return-19904-apmail-ws-axis-dev-archive=ws.apache.org@ws.apache.org>
Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org
Received: (qmail 24534 invoked by uid 500); 6 Mar 2003 22:05:36 -0000
Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
list-help: <mailto:axis-dev-help@ws.apache.org>
list-unsubscribe: <mailto:axis-dev-unsubscribe@ws.apache.org>
list-post: <mailto:axis-dev@ws.apache.org>
Delivered-To: mailing list axis-dev@ws.apache.org
Received: (qmail 24525 invoked from network); 6 Mar 2003 22:05:36 -0000
Date: 6 Mar 2003 22:07:20 -0000
Message-ID: <20030306220720.6498.qmail@nagoya.betaversion.org>
From: bugzilla@apache.org
To: axis-dev@ws.apache.org
Cc: 
Subject: DO NOT REPLY [Bug 17303]  -
    Invalid WSDL generated when using wrapped/literal
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

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.