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: JaxMe Issue Type: Bug Components: JaxMeXS Affects Versions: 0.5 Reporter: Christian Koppen JAXME produces invalid Java source files when the input schemas contains a certain combination of subtyping and 'sequence' elements. It's not easy to describe but I attach a test case to reproduce the behavior. The following code was generated. Code snippet 1: public class BHandler extends org.apache.ws.jaxme.impl.JMSAXElementParser { public class AHandler extends org.apache.ws.jaxme.impl.JMSAXGroupParser { ... } public class BHandler extends org.apache.ws.jaxme.impl.JMSAXGroupParser { ... } } This is invalid java code because a class must not contain another class with the same name (BHandler). Code snippet 2: public class CHandler extends org.apache.ws.jaxme.impl.JMSAXElementParser { public class GroupHandler extends org.apache.ws.jaxme.impl.JMSAXGroupParser { public class GroupHandler extends org.apache.ws.jaxme.impl.JMSAXGroupParser { public class AHandler extends org.apache.ws.jaxme.impl.JMSAXGroupParser { ... } public class BHandler extends org.apache.ws.jaxme.impl.JMSAXGroupParser { ... } ... } public class BbHandler extends org.apache.ws.jaxme.impl.JMSAXGroupParser { ... } ... } public class CHandler extends org.apache.ws.jaxme.impl.JMSAXGroupParser { ... } } GroupHandler and CHandler are both declared 2 times which is invalid. -- 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