ISSUE-34

multiple schemas for a single namespace

State:
CLOSED
Product:
Basic
Raised by:
Paul Downey
Opened on:
2006-04-21
Description:
"""
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
Related emails:
  1. ISSUE-34: multiple schemas for a single namespace (from dean+cgi@w3.org on 2006-04-21)
  2. RE: ISSUE-34: multiple schemas for a single namespace (from paul.downey@bt.com on 2006-04-21)
  3. RE: ISSUE-34: multiple schemas for a single namespace (from gcowe@origoservices.com on 2006-04-25)
  4. RE: ISSUE-34: multiple schemas for a single namespace (from paul.downey@bt.com on 2006-04-25)
  5. RE: ISSUE-34: multiple schemas for a single namespace (from Paul.V.Biron@kp.org on 2006-04-26)
  6. Re: ISSUE-34: multiple schemas for a single namespace (from gcowe@origoservices.com on 2006-04-28)
  7. RE: ISSUE-34: multiple schemas for a single namespace (from paul.downey@bt.com on 2006-04-28)
  8. Agenda: XML Schema Patterns for Databinding Telcon 2 May 2006 (from paul.downey@bt.com on 2006-04-28)
  9. Minutes from XML Schema Patterns for Databinding call 2 May 2006 (from paul.downey@bt.com on 2006-05-02)
  10. RE: Minutes from XML Schema Patterns for Databinding call 2 May 2006 (from paul.downey@bt.com on 2006-05-02)
  11. Agenda: XML Schema Patterns for Databinding Telcon 9 May 2006 (from paul.downey@bt.com on 2006-05-05)
  12. Minutes from XML Schema Patterns for Databinding call 9 May 2006 (from paul.downey@bt.com on 2006-05-09)
  13. Re: Minutes from XML Schema Patterns for Databinding call 9 May 2006 (from petexmldev@tech-know-ware.com on 2006-05-10)
  14. ISSUE-34 [wsi_wsbasic] Proposed clarification for BP12002 (from paul.downey@bt.com on 2006-06-06)
  15. Agenda (Revised): XML Schema Patterns for Databinding Telcon 6 June 2006 (from paul.downey@bt.com on 2006-06-06)
  16. Minutes from XML Schema Patterns for Databinding call 6 June 2006 (from paul.downey@bt.com on 2006-06-06)
  17. Agenda: XML Schema Patterns for Databinding Telcon 13 June 2006 (from paul.downey@bt.com on 2006-06-13)
  18. Minutes from XML Schema Patterns for Databinding call 13 June 2006 (from paul.downey@bt.com on 2006-06-13)
  19. Agenda: XML Schema Patterns for Databinding Telcon 27 June 2006 (from paul.downey@bt.com on 2006-06-26)
  20. Minutes: XML Schema Patterns for Databinding Telcon 27 June 2006 (from paul.downey@bt.com on 2006-06-27)

Related notes:

2006-06-06: closed with no action, Origo will push this further in the WS-I