On Sep 7, 2006, at 12:10 PM, Raymond Feng wrote:
and
physicalType: OMElement.class
logicalType: QName{http://example.com, order}
When we try to populate the OMElement for "order" with Customer and
String, we have to create child OMElements under "order" and the
child elements requires QNames. Where can we get the corresponding
child element QNames? Axiom doesn't provide access to the XSD model
and we cannot look them up by the order QName.
This seems like a problem with Axiom :-) Well not really, just the
issue that you need access to the XML schema and it's not providing it.
I'm thinking here that the logicalType is actually an element QName
as it is an instance not a type. We are trying to generate the XML
<order>
<customer>
<string>
and need to know the "order" element name as well as its sub-elements.
IOW the Axiom databinding needs to know the schema involved. That is
an issue with Axiom (and DOM and other things without a built-in type
system) rather than XML itself. For example, for SDO we could have
physicalType: DataObject.class
logicalType: Type{Order.class} or Type{QName{http://example.com,
order}}
And for WSDL, do we only support single-part messages? If not, the
inputType for WSDL could be Object[] as well.
I'm not sure how WSDL applies here. I can see that for a multi-part
message (but all XML and not multi-part mime (attachments) :-) ) you
could have:
physicalType: OMElement[].class
logicalType: QName[]{ QName{example:order}, QName{xs:string} }
--
Jeremy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
