[ https://issues.apache.org/jira/browse/JAXME-102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jochen Wiedmann resolved JAXME-102. ----------------------------------- Resolution: Won't Fix Using jaxb:property is the way to resolve such conflicts that the specification endorses. Everything else would violate the specification. > No support for types of the same name in different namepaces > ------------------------------------------------------------ > > Key: JAXME-102 > URL: https://issues.apache.org/jira/browse/JAXME-102 > Project: JaxMe > Issue Type: Bug > Components: JaxMeXS > Affects Versions: 0.5 > Reporter: Christian Koppen > Attachments: testdata.zip > > > 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 { ... } -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: jaxme-dev-unsubscr...@ws.apache.org For additional commands, e-mail: jaxme-dev-h...@ws.apache.org