[ http://issues.apache.org/jira/browse/AXIS-1366?page=history ]
Alan Green updated AXIS-1366:
-----------------------------
Attachment: CommunityInformation.wsdl
I'm seeing the opposite problem with 1.2RC2: the hand-coded WSDL uses
elementFormDefault="qualified", but the generated WSDL omits the
elementFormDefault attribute.
This is a painful bug for us. I have attached "CommunityInformation.wsdl"
> Service re-creates incorrect WSDL
> ---------------------------------
>
> Key: AXIS-1366
> URL: http://issues.apache.org/jira/browse/AXIS-1366
> Project: Axis
> Type: Bug
> Components: WSDL processing
> Versions: current (nightly)
> Environment: Windows 2003 Server.
> JDK 1.4.2_03
> Reporter: Kevin Jones
> Assignee: Glen Daniels
> Attachments: AxisTest.wsdl, CommunityInformation.wsdl
>
> 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?
--
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
