In some cases, the WSDL part is typed by an XSD element instead of type. Do
we use the element QName instead of the type QName which needs to be
resolved in the XSD by the element QName?
Thanks,
Raymond
----- Original Message -----
From: "Jeremy Boynes" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Monday, August 28, 2006 2:28 PM
Subject: Re: XML Schema API to introspect WSDL part types?
Doesn't the QName alone provide enough information? I mean, why do we
need the full type definition, isn't it enough just to know the required
type?
--
Jeremy
On Aug 28, 2006, at 1:46 PM, Raymond Feng wrote:
Hi,
I ran into an issue when I try to introspect a WSDL portType to create
the WSDLServiceContract: We don't have the XML schema information
referenced by the WSDL.
We use WSDL4J to load WSDL files to resolve WSDL related metadata such
as PortType. As you know, a WSDL part in a message is usually typed by
either a XSD type or element. How do we resolve these XSD references? Do
we need a databinding-independent model such as XmlSchema (from Apache
ws-commons: http://ws.apache.org/commons/ XmlSchema/) or should we leave
it to the specific DataBinding extension (for example, SDO can resolve
it using XSDHelper)?
Any thoughts?
Thanks,
Raymond
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
