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

2009-04-09 Thread Christian Koppen (JIRA) 

 [ 
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 files.

 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

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

2009-04-09 Thread Christian Koppen (JIRA) 
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

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

2009-04-09 Thread Christian Koppen (JIRA) 

 [ 
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 files. 

 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
 Attachments: testdata.zip


 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

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

2009-04-09 Thread Christian Koppen (JIRA) 

[ 
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 understand right, I could rename the 
types (T in the example) to avoid name conflicts. I check this, although this 
is not the preferred way for me.

 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