[jira] Commented: (AXIS-1366) Service re-creates incorrect WSDL

[ax...@ws.apache.org]

The following comment has been added to this issue:

     Author: Dan Ciarniello
    Created: Sat, 16 Oct 2004 1:13 PM
       Body:
I think that this bug has a lot to do with some of the interoperability issues, expecially with .NET.  deploy.wsdd files generated with WSDL2Java reflect the value of the elementFormDefault value but since the WSDL generator always adds elementFormDefault="qualified", the service will often produce SOAP responses that do not match what the WSDL tells the client to expect.

For example, when elementFormDefault="unqualified", the service produces unqualified elements (xmlns="") but the WSDL is telling clients to expect qualified elements.  .Net, in particular, has problems with this but so do WSDL2Java-generated clients if the WSDL is set up in a particular way (see the attached WSDL).

---------------------------------------------------------------------
View this comment:
  http://issues.apache.org/jira/browse/AXIS-1366?page=comments#action_54250

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/AXIS-1366

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: AXIS-1366
    Summary: Service re-creates incorrect WSDL
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Axis
 Components: 
             WSDL processing
   Versions:
             current (nightly)

   Assignee: 
   Reporter: Kevin Jones

    Created: Thu, 20 May 2004 8:25 AM
    Updated: Sat, 16 Oct 2004 1:13 PM
Environment: Windows 2003 Server.
JDK 1.4.2_03

Description:
I create a Web Service from WSDL in which the Schema has elementFormDefault="unqualified" (in fact I just use the default)

I deploy the service *without* any WSDL.

I browse to the service using ?WSDL and I see that the schema in the WSDL uses elementFormDefault="qualified"

The bizarre thing is that if I generate a client from the WSDL the client sends the wrong request (everything is qualified) but the server still works, and the server sends the wrong reeponse (so far as the client is concerned as it uses unqualified elements) and the client accepts it.

It seems like the problem is that the server, when it generates the WSDL, doesn't know to use unqualified. Maybe another WSDD parameter is needed?


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira