[JAXME-102] No support for types of the same name in different namepaces

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 0.5
• Component/s: JaxMeXS
• Assignee: Unassigned
• Reporter: Christian Koppen
• Created: 09/Apr/09 11:55
• Updated: 09/Apr/09 15:05
• Resolved: 09/Apr/09 15:05

Description

JAXME produces invalid Java source files when the input schemas contain types with the same name in different namespaces.
Example:

First schema:
<schema targetNamespace="http://a" xmlns="http://www.w3.org/2001/XMLSchema">
<complexType abstract="true" name="T" />
</schema>

Second schema:
<schema targetNamespace="http://b" xmlns="http://www.w3.org/2001/XMLSchema" xmlns:a="http://a">
<import namespace="http://a" schemaLocation="a.xsd" />
<complexType abstract="true" name="T">
<complexContent>
<extension base="a:T" />
</complexContent>
</complexType>
</schema>

Generated java source file ObjectFactory.java contains:
public a.T createT() throws javax.xml.bind.JAXBException

{ ... }
public b.T createT() throws javax.xml.bind.JAXBException { ... }