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

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

The following issue has been updated:

    Updater: Dan Ciarniello (mailto:dciarniello@cityxpress.com)
       Date: Sat, 16 Oct 2004 1:29 PM
    Comment:
I've attached a WSDL file that illustrates how the elementFormDefault issue affects WSDL2Java.

1. Take the attached WSDL (which does not have elementFormDefault defined), generate server side classes and deploy with AdminClient and the generated deploy.wsdd.
2. Use WSDL2Java to generate client side classes from the generated WSDL.
3. Attempt to invoke the service.  A NullPointerException should be thrown.
4. Add elementFormDefault="qualified" to the WSDL and repeat steps 1 to 3.  This time, everything should work as expected.


    Changes:
             Attachment changed to AxisTest.wsdl
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://issues.apache.org/jira/browse/AXIS-1366?page=history

---------------------------------------------------------------------
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:29 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