[jira] Updated: (JAXME-102) No support for types of the same name in different namepaces

[ https://issues.apache.org/jira/browse/JAXME-102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Koppen updated JAXME-102: --- Attachment: testdata.zip A ZIP file containing two schema files and the generated java source

[jira] Created: (JAXME-103) A combination of subtyping and sequence causes generation of invalid java source code

A combination of subtyping and sequence causes generation of invalid java source code - Key: JAXME-103 URL: https://issues.apache.org/jira/browse/JAXME-103 Project:

[jira] Updated: (JAXME-103) A combination of subtyping and sequence causes generation of invalid java source code

[ https://issues.apache.org/jira/browse/JAXME-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Koppen updated JAXME-103: --- Attachment: testdata.zip A ZIP file containing two schema files and the generated java source

[jira] Commented: (JAXME-102) No support for types of the same name in different namepaces

[ https://issues.apache.org/jira/browse/JAXME-102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12697502#action_12697502 ] Christian Koppen commented on JAXME-102: No, I didn't use any customizations. If I

[jira] Resolved: (JAXME-102) No support for types of the same name in different namepaces

[ 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