W3C home > Mailing lists > Public > public-xsd-databinding@w3.org > April 2006

ISSUE-34: multiple schemas for a single namespace

From: Databinding Issue Tracker <dean+cgi@w3.org>
Date: Fri, 21 Apr 2006 16:07:39 +0000 (GMT)
To: public-xsd-databinding@w3.org
Message-Id: <20060421160739.4EE38BDA7@w3c4.w3.org>


ISSUE-34: multiple schemas for a single namespace

http://www.w3.org/2005/06/tracker/databinding/issues/34

Raised by: Paul Downey
On product: Basic

"""
When we implement a messaging service we typically have two schemas – one for
the request and one for the response. Each will share the same namespace.

 

In WSDL we have a request-response service with a request message and a response
message defined separately.

 

When using data binding tools to generate code from the WSDL (Apache Axis 1.3
WSDL2Java in our case) the target namespace is used to name the packages
containing the generated classes.

 

This causes a problem because the namespace in both schemas are the same. This
results in the data binding tool attempting to use the same package name for
both the classes representing the request and response schemas.

When element names collide in both schemas then only the element defined in the
first schema (the request schema) is processed. Note that element names are the
same but their structure will often be different (the response typically is more
complex than the request).

 

There are a number of ways to work around this problem including

·        Make the namespaces unique

·        Don’t use data-binding tools

 

We believe we are using schema namespacing correctly so are reluctant to do make
changes to them as this would cause a proliferation of namespaces for us. 

"""
George Cowe
Origo Services
Received on Friday, 21 April 2006 16:07:43 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 18 December 2010 18:20:37 GMT