| Key: |
AXIS-2235
|
| Type: |
Bug
|
| Status: |
Closed
|
| Resolution: |
Duplicate
|
| Priority: |
Major
|
| Assignee: |
Unassigned
|
| Reporter: |
clint dovholuk
|
| Votes: |
1
|
| Watchers: |
1
|
|
If you were logged in you would be able to see more operations.
|
|
|
|
Environment:
|
win xp pro, 1 gb ram, using resin 2/3 app server, jdk 1.5
|
|
| Resolution Date: |
14/Dec/05 12:14 AM
|
|
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
|
|
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 |
Show » |
made changes - 14/Dec/05 12:14 AM
| Field |
Original Value |
New Value |
|
Resolution
|
|
Duplicate
[ 3
]
|
|
Status
|
Open
[ 1
]
|
Closed
[ 6
]
|
|
Autogenerated WSDL does not qualify the wsdl:types at all
