[jira] Kommentiert: (JAXME-54) ISO-8859-1 encoding not working correctly.

[ http://issues.apache.org/jira/browse/JAXME-54?page=comments#action_65854 ] Jochen Wiedmann commented on JAXME-54: -- Charset is a Java 1.4 class. We cannot use that. ISO-8859-1 encoding not working correctly.

[jira] Kommentiert: (JAXME-58) IDREF handling does not follow JAXB spec (5.8.2)/reference implementation

[ http://issues.apache.org/jira/browse/JAXME-58?page=comments#action_12315891 ] Jochen Wiedmann commented on JAXME-58: -- A question which came up while discussing the feature: To resolve IDREF's, the parser will obviously create an internal Map of ID =

[jira] Kommentiert: (JAXME-58) IDREF handling does not follow JAXB spec (5.8.2)/reference implementation

[ http://issues.apache.org/jira/browse/JAXME-58?page=comments#action_12315892 ] Jochen Wiedmann commented on JAXME-58: -- Proposed way to resolve the issue; Forgetting for a moment, that the actual bean classes need changes, I'll suggest that we start

[jira] Geschlossen: (JAXME-59) CDMv2.01 schema cannot be compiled

[ http://issues.apache.org/jira/browse/JAXME-59?page=all ] Jochen Wiedmann closed JAXME-59: CDMv2.01 schema cannot be compiled -- Key: JAXME-59 URL: http://issues.apache.org/jira/browse/JAXME-59

[jira] Kommentiert: (JAXME-62) IllegalArgumentException on validation, length limit exceeded

[ http://issues.apache.org/jira/browse/JAXME-62?page=comments#action_12317128 ] Jochen Wiedmann commented on JAXME-62: -- Hmmm, the reason for the IllegalArgumentException is, that the check for maxLength occurs within setFoo() and not within the SAX

[jira] Aktualisiert: (JAXME-63) JaxMe (wrongly) accepts schema using group ref=... maxOccurs=unbounded/

[ http://issues.apache.org/jira/browse/JAXME-63?page=all ] Jochen Wiedmann updated JAXME-63: - Attachment: JAXME63.patch Patch for the problem. JaxMe (wrongly) accepts schema using group ref=... maxOccurs=unbounded/

[jira] Geschlossen: (JAXME-63) JaxMe (wrongly) accepts schema using group ref=... maxOccurs=unbounded/

[ http://issues.apache.org/jira/browse/JAXME-63?page=all ] Jochen Wiedmann closed JAXME-63: Fix Version: 0.5 Resolution: Fixed Assign To: Jochen Wiedmann Interesting ... you've found some of the (surprisingly few) problems in the XS

[jira] Aktualisiert: (JAXME-58) IDREF handling does not follow JAXB spec (5.8.2)/reference implementation

[ http://issues.apache.org/jira/browse/JAXME-58?page=all ] Jochen Wiedmann updated JAXME-58: - Attachment: idMap3.patch To keep the discussion open, a modified version of your patch. The IDREF properties should now be objects indeed. I am currently

[jira] Kommentiert: (JAXME-64) [PATCH] Maven plugin for JaxMe2

[ http://issues.apache.org/jira/browse/JAXME-64?page=comments#action_12318387 ] Jochen Wiedmann commented on JAXME-64: -- Marcus, your contribution is extremely welcome. In fact, Nacho is currently working on the mavenization of JaxMe itself. As Nacho

[jira] Aktualisiert: (JAXME-65) mixed=true attribute on complexTypes unsupported?

[ http://issues.apache.org/jira/browse/JAXME-65?page=all ] Jochen Wiedmann updated JAXME-65: - Attachment: JAXME-65.patch The ChoiceHandlerSG did not treat a choice with minOccurs=0 as optional. mixed=true attribute on complexTypes unsupported?

[jira] Geschlossen: (JAXME-65) mixed=true attribute on complexTypes unsupported?

[ http://issues.apache.org/jira/browse/JAXME-65?page=all ] Jochen Wiedmann closed JAXME-65: Fix Version: 0.6 Resolution: Fixed Assign To: Jochen Wiedmann Patch applied to trunk and 0.5 branch. mixed=true attribute on complexTypes

[jira] Geschlossen: (JAXME-58) IDREF handling does not follow JAXB spec (5.8.2)/reference implementation

[ http://issues.apache.org/jira/browse/JAXME-58?page=all ] Jochen Wiedmann closed JAXME-58: Fix Version: 0.6 Resolution: Fixed Assign To: Jochen Wiedmann After initial work on merging the JAXME-28 branch, I changed my mind and decided

[jira] Geschlossen: (JAXME-67) Building from Source: Missing Files

[ http://issues.apache.org/jira/browse/JAXME-67?page=all ] Jochen Wiedmann closed JAXME-67: Fix Version: 0.6 Resolution: Fixed Assign To: Jochen Wiedmann Fixed in trunk and 0.5 branch. Thanks, in particular for resolving the problems

[jira] Zugewiesen: (JAXME-74) JAXP Transform seems fails

[ http://issues.apache.org/jira/browse/JAXME-74?page=all ] Jochen Wiedmann reassigned JAXME-74: Assign To: Jochen Wiedmann JAXP Transform seems fails -- Key: JAXME-74 URL:

[jira] Kommentiert: (JAXME-72) Generated structures that has xsd:QName types does not marshal correcly.

[ http://issues.apache.org/jira/browse/JAXME-72?page=comments#action_12358777 ] Jochen Wiedmann commented on JAXME-72: -- The repository was converted to subversion since the last release. Try http://svn.apache.org/repos/asf/webservices/jaxme

[jira] Geschlossen: (JAXME-75) List returning more that the types required.

[ http://issues.apache.org/jira/browse/JAXME-75?page=all ] Jochen Wiedmann closed JAXME-75: Resolution: Invalid The error is in your application: List children = sh.getLibraryReference();

[jira] Erstellt: (JAXME-80) Mixed content with empty elemen tcauses NPE

Mixed content with empty elemen tcauses NPE --- Key: JAXME-80 URL: http://issues.apache.org/jira/browse/JAXME-80 Project: JaxMe Type: Bug Versions: 0.5 Reporter: Jochen Wiedmann Priority: Minor The following

[jira] Created: (JAXME-83) Element references are referencing the global elements type interface and not the element itself

Element references are referencing the global elements type interface and not the element itself Key: JAXME-83 URL: http://issues.apache.org/jira/browse/JAXME-83

[jira] Created: (JAXME-84) minOccurs=0 not recognized in choice, if the choice is within an extension

minOccurs=0 not recognized in choice, if the choice is within an extension Key: JAXME-84 URL: http://issues.apache.org/jira/browse/JAXME-84 Project: JaxMe Issue

[jira] Resolved: (JAXME-84) minOccurs=0 not recognized in choice, if the choice is within an extension

[ http://issues.apache.org/jira/browse/JAXME-84?page=all ] Jochen Wiedmann resolved JAXME-84. -- Resolution: Fixed The problem turned out to be, in fact, in the XS layer. If an extended element has empty content, then the resulting content is actually

[jira] Resolved: (JAXME-77) Java parser chokes on import packagename.*

[ http://issues.apache.org/jira/browse/JAXME-77?page=all ] Jochen Wiedmann resolved JAXME-77. -- Fix Version/s: 0.6 Resolution: Fixed Assignee: Jochen Wiedmann Applied to 0.5 and 0.6 branch. Java parser chokes on import packagename.*

[jira] Commented: (JAXME-89) Multiple implements clauses are not supported

[ http://issues.apache.org/jira/browse/JAXME-89?page=comments#action_12455301 ] Jochen Wiedmann commented on JAXME-89: -- I haven't yet worked out why, but the AntLRTest fails after applying your patch: The class name must not be null or

[jira] Resolved: (JAXME-89) Multiple implements clauses are not supported

[ http://issues.apache.org/jira/browse/JAXME-89?page=all ] Jochen Wiedmann resolved JAXME-89. -- Fix Version/s: 0.6 Resolution: Fixed Assignee: Jochen Wiedmann Applied to 0.5 branch and trunk. Multiple implements clauses are not

[jira] Resolved: (JAXME-92) JavaSource has at least two NPE sources

[ https://issues.apache.org/jira/browse/JAXME-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Wiedmann resolved JAXME-92. -- Resolution: Won't Fix This is obviously a matter of programming style and taste. The JavaJS

[jira] Commented: (JAXME-94) startElement method larger than 64KB when using a large amount of complexType's

[ https://issues.apache.org/jira/browse/JAXME-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12524019 ] Jochen Wiedmann commented on JAXME-94: -- Had some time yesterday to inspect it. My first impressions: - This

[jira] Resolved: (JAXME-95) JavaParser.parseObject() handles inner interfaces incorrectly

[ https://issues.apache.org/jira/browse/JAXME-95?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Wiedmann resolved JAXME-95. -- Resolution: Fixed Applied, thank you! JavaParser.parseObject() handles inner interfaces

[jira] Resolved: (JAXME-100) Can't have attribute and element with the same name

[ https://issues.apache.org/jira/browse/JAXME-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Wiedmann resolved JAXME-100. --- Resolution: Invalid Assignee: Jochen Wiedmann Use jaxb:property name=SomeElement/ on

[jira] Resolved: (JAXME-99) Generate 'Serializable' implementation classes

[ https://issues.apache.org/jira/browse/JAXME-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Wiedmann resolved JAXME-99. -- Resolution: Invalid Assignee: Jochen Wiedmann Use xjc:serializable. See

[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

[jira] Resolved: (JAXME-104) wrong xsd:pattern handling

[ https://issues.apache.org/jira/browse/JAXME-104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Wiedmann resolved JAXME-104. --- Resolution: Fixed Fix Version/s: 0.6 Assignee: Jochen Wiedmann Applied, thank

[jira] Resolved: (JAXME-105) can't generate get list method with element has maxOccurs=unbounded

[ https://issues.apache.org/jira/browse/JAXME-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Wiedmann resolved JAXME-105. --- Assignee: Jochen Wiedmann Resolution: Invalid I assume, that you mean no corresponding