I'd be interested in knowing this as well as I am currently creating WSDL files that
have attributes in the schemas.
-Original Message-
From: Michael Zurke [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 12, 2003 2:05 PM
To: [EMAIL PROTECTED]
Subject: Re:Re: support of xml attributes
it'
settle
down.
-Original Message-From: Mr. Document Service
[mailto:[EMAIL PROTECTED]Sent: Thursday, June 12, 2003 12:27
PMTo: [EMAIL PROTECTED]Subject: RE: Re: support of
xml attributes
are valid XML Schema 1.0
constructs.
WS-I Basic Profile mandates the use of
are valid XML Schema 1.0 constructs.
WS-I Basic Profile mandates the use of XML Schema as the type system for WSDL descriptions of Web Services.
It does not seem like AXIS is WS-I Basic Profile compliant. Does anyone know if there are plans to fix this? If AXIS can not support all XML Schema 1.
My understanding is that attributes get converted to SOAPElements as defined by the
JAX-RPC spec.
"The JAX-RPC specification does not specify a standard Java mapping for a
xsd:complexType with the xsd:attribute. So the message part in the
DoAnotherExample message is mapped as a SOAPElement." see
