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]
