- From: Glen Daniels <gdaniels@sonicsoftware.com>
- Date: Mon, 4 Oct 2004 11:24:29 -0400
- To: "Jeehong Min" <jeehongm@parasoft.com>, "WS Description List" <www-ws-desc@w3.org>
Jeehong: As long as there is no overlap between the component definitions in multiple schema containers for the same namespace, I think this should work just fine. If there is overlap, we simply need to follow what the schema spec says about how to resolve repeated components in a schema (I'm not sure, though, if that's fault, first-one-wins, or last-one-wins...). --Glen > -----Original Message----- > From: www-ws-desc-request@w3.org > [mailto:www-ws-desc-request@w3.org] On Behalf Of Jeehong Min > Sent: Monday, September 27, 2004 12:48 PM > To: www-ws-desc@w3.org > Subject: Can multiple inline schemas have same targetNamespace? > > I would appreciate it if you could address the following > issue that I have seen in WSDLs of 2 customers in the past month. > > One vendor's SOAP stack is creating WSDLs with multiple > inline schemas that have the same namespace. > > Here's an example: > <wsdl:definition> > <wsdl:types> > <xs:schema targetNamespace="a"> > types and elements > </xs:schema> > <xs:schema targetNamespace="a"> > different types and elements > </xs:schema> > <xs:schema targetNamespace="b"> > whatever > </xs:schema> > </wsdl:types> > ... > <wsdl:definition> > > It's not clear to me whether the above is legal or not (two > schemas with the same targetNamespace="a"). Should XML > parsers for WSDL be smart enough to handle the above? Or > should parsers report errors? > > -- > Jeehong Min > Software Engineer > SOAPtest Development > Parasoft Corporation > > "We Make Software Work" >
Received on Monday, 4 October 2004 15:32:01 UTC