2) Adb databinding fails to generate classes and fields for enums derived from string. For a schema complex type attribute like this: <xs:simpleType> <xs:restriction base="xs:string"> <xs:enumeration value="SUCCESS"/> <xs:enumeration value="FAILURE"/> </xs:restriction> </xs:simpleType> no field appears in the respcetive Java class generated from the complex type having this attribute - and no class is generated from the enum type. Fortunately xmlbeans bindings handles this perfectly - an emum style Java class is generated and appropriate fields appear. BTW early versions of axis1 had also problems with such enum ;) Do the developers follow similar path ? ;)
axis2 1.1.1 does not handle enum and restrictions properly. Can you please check with a nightly build? if you get errors still please log a jira and attach your wsdl. 2a) The generated adb Java class names are just ugly, like this:
xsdtypename_typex for x=1,2,3,... . This is not a problem but the "_typex" suffixes are just disturbing. Has anyone also met those problems ? Regards, J.K. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Amila Suriarachchi, WSO2 Inc.
