http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2291
*** shadow/2291 Fri Jun 22 12:06:11 2001
--- shadow/2291.tmp.22201 Fri Jun 22 12:18:43 2001
***************
*** 31,33 ****
--- 31,51 ----
BufferedReader rd =new BufferedReader(new InputStreamReader(is));
Or, they will not be able to correctly read META-INF/services/
+
+ ------- Additional Comments From [EMAIL PROTECTED] 2001-06-22 12:18 -------
+ This is an issue that has been discussed at length but never resolved. The
+ problem is that on OS/390 and other non-ASCII systems like AS/400, files that
+ are in a .jar are generally ASCII files. However, if you want to
+ modify/override this file, you'd usually create a new file in the HFS (or IFS)
+ and place that file ahead of the .jar file in the CLASSPATH. That file, being
+ in the file system, would normally be an EBCDIC file even though it has the same
+ name as the file in the .jar and that file should have an EBCDIC reader, not an
+ ASCII or UTF-8 reader. Unfortunately, when we do a
+ ClassLoader.getResourceAsStream, there is no reliable way of knowing where the
+ resource was located (.jar vs file system) and therefore no way to know what
+ encoding to use.
+
+ Perhaps we could have system properties to set the encoding for each META-INF/
+ and .properties file although this seems like a cumbersome solution.
+
+ Thoughts?
\ No newline at end of file
