Autogenerated WSDL does not qualify the wsdl:types at all

• Key: AXIS-2235
• Type: Bug
• Status: Closed
• Resolution: Duplicate
• Priority: Major
• Assignee: Unassigned
• Reporter: clint dovholuk
• Component/s: WSDL processing
• Affects Version/s: 1.2RC3, 1.2, 1.2.1

Description

I have noticed that now when axis autogenerates wsdl's the wsdl does not correctly namespace qualify the "types" element, thus when processed and consumed an error is thrown stating that "whichever" element can't be found. Editing the wsdl by hand to qualify the types element fixes the problem.

for example, an autogenerated wsdl will look like:
     <wsdl:definitions targetNamespace="myWebApp:TestSubclass">
          <!--
               WSDL created by Apache Axis version: 1.2.1
               Built on Jun 14, 2005 (09:15:57 EDT)
           -->
<types>

and not :
     <wsdl:definitions targetNamespace="myWebApp:TestSubclass">
          <wsdl:types>

it's minor, but it's always reproducable... I've tried using 1.2rc3 and on (1.2, and 1.2.1)

-Clint

Comments

[clint dovholuk]

well i didn't get the option to set the "priority" on this.. i don't think it's "critical", but maybe?

cwd

[clint dovholuk]

another possibility...

it seems that previous versions of axis (prior to 1.2rc3 afaict) used to set the default namespace to that of "wsdl" such as: xmlns="http://schemas.xmlsoap.org/wsdl/"

this is no longer supplied in generated wsdl's thus the <types> tag is not qualified properly - i think...

cwd

[Davanum Srinivas]

Have u tried Axis 1.3?

[clint dovholuk]

yes, the same problem is in axis 1.3 as well. axis 1.3 has other issues (i've not had time to post yet) which prevent me from using it though. (i need to create a test case for that issue so i can submit a bug)

cwd

[Paul Barry]

Are there any plans to work on this bug? I have a very simple example of this problem that I submitted to the mailing list a while ago:

http://marc.theaimsgroup.com/?l=axis-user&m=113045538011182&w=2

From reading other issues on the mailing list, it seems that other people using Axis 1.2.1 are able to generate WSDL with <wsdl:types> instead of just <types>. Does anyone know what the difference is yet? Why it generates <types> for me in a simple example yet other seem to get <wsdl:types>? I am using resin 3.0.14 and JDK 1.5 on Windows XP, in case that is relevant.

[Tom Jordahl]

I don't see this bug on Axis 1.2.1 or 1.3. I have WSDL that has both the default namespace and the wsdl prefix.

[clint dovholuk]

can you post the wsdl that you use so I could test it and figure out what i'm doing "wrong"?

thanks,
cwd

[clint dovholuk]

this is still a problem.

anybody have any thoughts on this?

cwd

[clint dovholuk]

it seems that this is an issue with our Resin application server... For fun I brought our app up on a Tomcat install and it works just fine...

Any ideas on why Resin (www.caucho.com) causes the problem?

Thanks,
-Clint

[clint dovholuk]

so after a lot of digging, i found that putting this:


  <system-property javax.xml.parsers.DocumentBuilderFactory="org.apache.xerces.jaxp.DocumentBuilderFactoryImpl"/>
  <system-property javax.xml.parsers.SAXParserFactory="org.apache.xerces.jaxp.SAXParserFactoryImpl"/>

into the resin-web.config (resin 3) fixes the issue.

this can be closed i guess, but it'd be nice to see this documented somewhere as an 'issue'

cwd

[Tom Jordahl]

Why does the XML parser affect this? What does Resin use instead of Xerces, Crimson? I would say you need to file a bug against the parser that isn't adding the namespace...

[Tom Jordahl]

duplicate of Axis-2336.