I think the xsi attributes shown be handled as built-in since they are part of XSD. The extension mechanism should be reserved for WSDL extensions.
Arthur Ryman,
IBM Software Group, Rational Division
blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: [EMAIL PROTECTED]
| "Jeremy Hughes"
<[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED] 09/12/2006 04:57 AM
|
|
I think this should be handled like any other extension. Anything not
in the WSDL namespace is an extension to the WSDL. If we start
'special-casing' extensions then we could find other extensions would
like to do the same.
Jeremy
On 9/12/06, Oshani Seneviratne <[EMAIL PROTECTED]> wrote:
> Hi Graham and all,
>
> Even in the DOMWSDLReader, I assume that parseExtensionAttributes
> method was not intended to handle this. I'm referring to the comment
> "//TODO handle xsi attrs elsewhere, without need to register". (Please
> correct me if I'm wrong on this! )
>
> So, theoretically as you asked, how about having a method like
> parseExtensionAttributeSchema (or whatever the name) which gets called
> from the parseExtensionAttributes? We could also have a schema
> implementation like ExtensionAttributeSchema that could represent such
> external schemas. (Or maybe ImportedSchema could be used here).
> Any comments?
>
> Also, just to clarify, in the WSDL fragment you've given there are 2
> schema locations for 1 attribute. Is that possible?
>
> > <description targetNamespace="http://example.com/bank"
> > xmlns="http://www.w3.org/2006/01/wsdl"
> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> > xsi:schemaLocation=
> > "http://www.w3.org/2006/01/wsdl
> > http://www.w3.org/2006/01/wsdl/wsdl20.xsd
> > http://www.w3.org/2001/XMLSchema
> > http://www.w3.org/2001/XMLSchema.xsd" >
> >
>
> Thanks and Regards,
> Oshani
>
> ---------------------------------------------------------------------
> 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]
