> Hi, I have created a set of schemas for messages that i need to exchange
> between services. I set the targetNamespace
> ="http://mycompany/services/abc"
> and the root elements have names like FindCustomerRequest,
> FindCustomerResponse, CreateCustomerRequest and so on.
>
> In Biztalk when a message of any of the above comes in, it validates
> correctly because the engine sets the subscription to
> "http://mycompany/services/abc#FindCustomerRequest" .
>
> I also managed to create a webservice with these XSDs. However when
> creating
> a proxy i got an error saying that the targetNamespace was duplicated
> across
> schemas. The only way the system will allow me to proceed is if i change
> the
> targetNamespace of everyone of them and add something to it (for instance,
> the root element name) . Is this behavior expected? Should i make every
> targetnamespace unique? the thing is, all the XSDs import an architectural
> schema which defines the core types and there isnt anything special in the
> XSD which is why i left the targetNamespace to be common. Perhaps this is
> the
> wrong approach/
>
> Anyone care to comment?
>
> TIA,
> Benjy

"Priya Lakshminarayanan" wrote:

> If two schemas A and B have a import relationship where A imports B, then
> their targetNamespaces should be different. If you want to keep their
> targetNamespace the same, you should use xs:include and not xs:import. ie A
> includes B
>
> Thanks,
> Priya
>
> "BizTalk Benjamin" <BizTalkBenjamin@discussions.microsoft.com> wrote in
> message news:F4AE9C6E-3895-4EBA-AC7D-BBBDA10EFBEA@microsoft.com...
> > Hi, I have created a set of schemas for messages that i need to exchange
> > between services. I set the targetNamespace
> > ="http://mycompany/services/abc"
> > and the root elements have names like FindCustomerRequest,
> > FindCustomerResponse, CreateCustomerRequest and so on.
> >
> > In Biztalk when a message of any of the above comes in, it validates
> > correctly because the engine sets the subscription to
> > "http://mycompany/services/abc#FindCustomerRequest" .
> >
> > I also managed to create a webservice with these XSDs. However when
> > creating
> > a proxy i got an error saying that the targetNamespace was duplicated
> > across
> > schemas. The only way the system will allow me to proceed is if i change
> > the
> > targetNamespace of everyone of them and add something to it (for instance,
> > the root element name) . Is this behavior expected? Should i make every
> > targetnamespace unique? the thing is, all the XSDs import an architectural
> > schema which defines the core types and there isnt anything special in the
> > XSD which is why i left the targetNamespace to be common. Perhaps this is
> > the
> > wrong approach/
> >
> > Anyone care to comment?
> >
> > TIA,
> > Benjy
>
>