DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=29748>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=29748 Invalid encoding name "GBK". ------- Additional Comments From [EMAIL PROTECTED] 2004-07-06 21:57 ------- Hi Shiva, I successfully reproduced the problem using WebSphere Studio Application Developer(WSAD) version 5.1. WSAD runs WebSphere 5.0 as a WebSphere Test Environment. WebSphere probably ships with various versions of xalan.jar. I tried replacing the old xalan.jar file under lib directory in WebSphere with the version 2.6.0 of xalan.jar. However, it did not resolve the issue. It appeared to me that at runtime, WebSphere picked up a different version of xalan from one of its libraries. To resolve this issue, you need to ensure that version 2.6.0 of xalan.jar file is picked up first in runtime classpath. I added xalan.jar file to server classpath in WSAD. This included the version 2.6.0 of xalan.jar in the classpath before including other WebSphere specific libraries. The problem went away and I was able to see the page in browser. You can find out version of xalan.jar file by running class org.apache.xalan.Version. You can add xalan.jar file to JVM classpath using "Administrative Console" in WebSphere. In "Administrative Console", Go to Server->Application Server- >server1->Process Definition->Java Virtual Machine. Provide the "Classpath" entry for absolute path to xalan.jar. Let me know if this helps. Yash Talwar --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
