PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL BE LOST SOMEWHERE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3106 *** shadow/3106 Mon Aug 13 02:47:36 2001 --- shadow/3106.tmp.21879 Mon Aug 13 02:47:36 2001 *************** *** 0 **** --- 1,27 ---- + +============================================================================+ + | incorrect discover of SAXParser | + +----------------------------------------------------------------------------+ + | Bug #: 3106 Product: XalanJ2 | + | Status: NEW Version: 2.2.x | + | Resolution: Platform: Other | + | Severity: Blocker OS/Version: Other | + | Priority: Other Component: org.apache.xalan | + +----------------------------------------------------------------------------+ + | Assigned To: [EMAIL PROTECTED] | + | Reported By: [EMAIL PROTECTED] | + | CC list: Cc: | + +----------------------------------------------------------------------------+ + | URL: | + +============================================================================+ + | DESCRIPTION | + I'm using an EBCDIC(390) machine. Xalan is running at 0%. The only thing that + makes Xalan unusable is the use of a files included inside the jar file. On + EBCDIC machines, the ".res" and ".properties" files are incrrectly read. When i + extract all files in jar, and translete ".res" and ".properties" into EBCDIC, + Xalan is 100% usable. + To make Xalan runnable i must: + 1) delete the "services" directory + 2) extract & translate .res and .properties into EBCDIC + 3) include them into .jar file again + + the Xalan is running 100%. \ No newline at end of file
