DO NOT REPLY [Bug 15512] New: - Current Xerces code as compiled by 1.3 javac produces invalid classfile

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15512>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15512

Current Xerces code as compiled by 1.3 javac produces invalid classfile

           Summary: Current Xerces code as compiled by 1.3 javac produces
                    invalid classfile
           Product: Xerces2-J
           Version: 2.2.1
          Platform: PC
               URL: http://developer.java.sun.com/developer/bugParade/bugs/4
                    793774.html
        OS/Version: Linux
            Status: NEW
          Severity: Major
          Priority: Other
         Component: Other
        AssignedTo: xerces-j-dev@xml.apache.org
        ReportedBy: jesse.glick@netbeans.com


See the BugParade report for background.
src/org/apache/xerces/impl/xpath/regex/Token.java in the Xerces source tree
contains some Unicode character literals which, if compiled by the version of
javac found in JDK 1.3, may produce technically invalid class files (using
non-normalized UTF-8) which some VMs may refuse to load.

Fortunately a workaround in Xerces sources should probably be simple:
blockRanges and viramaString and the like can simply be made into char[].
Probably a shade faster at runtime, though perhaps slower to load the class.

---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org