Hi all,
Tryin to switch to axis 1.1 but it seems to me that enum support has changed
in WSDL2Java. What seemed
to work fine under 1.0 generated from a wsdl:
<s:element name="geslacht" minOccurs="1" maxOccurs="1" nillable="false" >
<s:simpleType>
<s:restriction base="s:string">
<s:enumeration value="M"/>
<s:enumeration value="V"/>
</s:restriction>
</s:simpleType>
</s:element>
Which is part of a complext type. Generated in the wsdd file:
<typeMapping
xmlns:ns="http://www.vecozo.nl/COV/";
qname="ns:Verzekerde>geslacht"
type="java:nl.iza.vecozo.axis.Geslacht"
serializer="org.apache.axis.encoding.ser.EnumSerializerFactory"
deserializer="org.apache.axis.encoding.ser.EnumDeserializerFactory"
encodingStyle=""
/>
And all worked well. Now under 1.1 it seems something has changed. First
thing is that the
generated wsdd file no longer holds the type mapping for the enum/simpletype
above. Then
the service wont function untill i put it in there manually before i deploy.
However from the
axis index.html page when i try to acces the wsdl file online for the
deployed service, that
gives the fault :
AXIS error
Sorry, something seems to have gone wrong... here are the details:
Fault - makeTypeElement() was told to create a type
"{http://www.vecozo.nl/COV/}Verzekerde>geslacht", with no containing element
AxisFault
faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.generalException
faultSubcode:
faultString: makeTypeElement() was told to create a type
"{http://www.vecozo.nl/COV/}Verzekerde>geslacht", with no containing element
faultActor:
faultNode:
faultDetail:
To cut a long story short either i deploy a working service with manually
editing in the wsdd and i live
with the wsdl not being available online or i have a non working service in
wich the ?wsdl works...
Any ideas greatly appreciated, i tried some things allready but really
puzzled now what causes this behavior.
Sincere greetings,
Leo de Blaauw
IZA/Groningen
