Community
Participate
Working Groups
EclipseLink fails to correctly escape certain characters (presumably past a certain range) when encoding is set to US-ASCII, and therefore differs from the Sun JAXB implementation. Example: JAXBElement<String> e = objFactory.createE("G\u00F6del & his friends"); class com.sun.xml.bind.v2.runtime.JAXBContextImpl US-ASCII <?xml version="1.0" encoding="US-ASCII" standalone="yes"?> <e>Gödel & his friends</e> class org.eclipse.persistence.jaxb.JAXBContext US-ASCII <?xml version="1.0" encoding="US-ASCII"?> <e>G?del & his friends</e>
Created attachment 213021 [details] Core - Fix
Created attachment 213022 [details] MOXy - Fix
Created attachment 213393 [details] MOXy - Test Cases
Created attachment 213394 [details] MOXy - Test Cases
Created attachment 213395 [details] MOXy - Test Cases
Created attachment 213398 [details] Core - Fix
Created attachment 213400 [details] MOXy - Fix
Created attachment 213403 [details] MOXy - Test Cases (2.3.3)
Created attachment 213404 [details] Core - Fix (2.3.3)
Created attachment 213405 [details] MOXy - Fix (2.3.3)
Fix checked into trunk at rev: 11074 Fix checked into 2.3.3 at rev: 11075 Code reviewed by: Denise Smith Fix Details: Check to see if the character can be handled in the charset, if not escape it.
Reopeining due to NPE occuring in the SDO tests.
Created attachment 213456 [details] Core - Fix (Part 2) To address the NPE that were occurring in the SDO test cases.
Fix checked into trunk at rev: 11084 Fix checked into 2.3.3 at rev: 11085
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink