Sorry, no help. I'm having the same problem. It seems to me that the behaviour is locked to rpc style with the xsi-stuff. I'm also running doc/lit and I didn't have any problems with RC3 either, but unfortunately it ended up in 1.2-final. It seems related to " dotnet_soapenc_bugfix is "blindly" reset" [1] in Jira. I thought I had a work around, but since then I haven't been able to get it right again. I'm also doing XML Schema validation and I also expect interoperability problems.
It seems to come when using service specific configuration in ex. Server-config.wsdd. Regards Brian [1] http://issues.apache.org/jira/browse/AXIS-1976 -----Original Message----- From: David Kocher [mailto:[EMAIL PROTECTED] Sent: 20. maj 2005 15:47 To: [email protected] Subject: xsi:type attribute not set correctly Dear all, We have a derived type from short in our schema such as: <xs:simpleType name="MyDerivedFromShortType"> <xs:restriction base="xs:short"> <xs:minInclusive value="1"/> <xs:maxInclusive value="100"/> </xs:restriction> </xs:simpleType> When sending an instance document (using document/literal) over the wire with axis (1.2), it is serialized as: <ns2:MyDerivedFromShort xsi:type="xsd:short">99</ns2:MyDerivedFromShort> However, I this seems to be incorrect, as MyDerivedFromShort is derived (!) from xs:short but not xs:short itself. When parsing this with Xerces it will throw Validation error: LineNumber: 48 ColumnNumber: 2883 Message: cvc-elt.4.3: Type 'xsd:short' is not validly derived from the type definition, 'MyDerivedFromShortType', of element 'ns2:MyDerivedFromShort'.: I just upgraded to 1.2 final; as far as I can tell this bug was not present in the latest release candidate. Please let me know if I missed something or if there is any known workaround. Thanks! -dk
