Hi, Ravindra
When the browser uses Java plug-in version 1.4+, the Xalan.jar, xercesImpl.jar and xml-apis.jar files specified by the archive param of an applet will NOT be used by the applet. The jar files that your applet is using are those bundled with the Java plug-in (older version of Xalan).
To make the applet using the new version of xalan, you have to add xalan.jar file to the endorsed directory of where the Java plug-in is installed.
Hope it helps,
Christine Li
XSLT Development
IBM Toronto Lab
Tel: (905)413-2601
Email: [EMAIL PROTECTED]
| <[EMAIL PROTECTED]>
12/21/2004 08:39 AM |
|
Hi Christine Li,
Thanks for your time and reply. I apologize not making my requirement clear.
These changes are required inside an applet which gets launched by browser Java(TM) Plug-in: Version 1.4.2_06.
I downloaded the latest Xalan 2.6.0 from the link provided by you. I have added all this jars in the archive param tag xalan.jar;xercesImpl.jar;xml-apis.jar
However I got the following error.
java.lang.ExceptionInInitializerError
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Unknown Source)
at org.apache.xalan.serialize.SerializerFactory.getSerializer(Unknown Source)
at org.apache.xalan.transformer.TransformerImpl.createResultContentHandler(Unknown Source)
at org.apache.xalan.transformer.TransformerImpl.createResultContentHandler(Unknown Source)
at org.apache.xalan.transformer.TransformerImpl.transform(Unknown Source)
at org.apache.xalan.transformer.TransformerImpl.transform(Unknown Source)
Please do let me know the following.
1. Is there any changes further required to be done on CharInfo.java. If yes please do let me know , so that I can go ahead with decompiling the class file and to make changes.
2. Is there any changes need to be done on ..properties files? . If yes please do let me know the changes.
3. Any missing inputs while executing on browser….
It could be of great favor if I get necessary modified source files.
Once again thanks for your time ..
Thanks,
Ravindra
-----Original Message-----
From: Christine Li [mailto:[EMAIL PROTECTED]
Sent: Monday, December 20, 2004 9:10 PM
To: Ravindra Govindaswamy(WT01 - EMBEDDED & PRODUCT ENGINEERING SOLUTIONS)
Cc: [EMAIL PROTECTED]
Subject: Re: jre1.4.2_05 and XML_ENTITIES_RESOURCE
Hi, Ravindra
You can download Xalan 2.6.0 release from http://www.apache.org/dyn/closer.cgi/xml/xalan-j . It includes the changes. To replace the version of Xalan distributed with JRE 1.4.2_05, please read http://xml.apache.org/xalan-j/faq.html#faq-N100CC
hopefully it helps,
Christine Li
XSLT Development
IBM Toronto Lab
Tel: (905)413-2601
Email: [EMAIL PROTECTED]
| <[EMAIL PROTECTED]>
12/20/2004 06:52 AM |
|
Hi Jycli,
I am having the same problem (XALANJ-1943) for which you have provided the patch.
I modified the CharInfo.java after decompiling to accept the properties files and recreated the jar.
However the problem still exists. Might be I have missed out some vital stuff.
Could it be possible to pass me all the modified files required to resolve this plug-in issue.
I am facing slippage in my deliverables because of this issue.
Thanks for your time.
Regards,
Ravindra
Modified: xml-xalan/java/src/org/apache/xml/serializer CharInfo.java HTMLEntities.properties output_html.properties output_xml.properties XMLEntities.properties xml-xalan/java/xdocs/sources/xalan usagepatterns.xml
Committer's log entry: Patch from Christine Li ([EMAIL PROTECTED]). Changed Char Info so that it allows descriptions of entities to be specified as a properties file in addition to a Xalan-specific resource file format. The code previously always assumed a Xalan-specific resource file format, for both user-supplied descriptions of entities, and for those supplied with Xalan-J. The security restrictions of applets are such that an applet that relies on a copy of Xalan-J in the Java run-time would find that Xalan-J would be unable to read the default entities file that is packaged with the JRE on the applet's behalf - it can only do so with properties, via Resource Bundle.
Confidentiality Notice The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain confidential or privileged information. If you are not the intended recipient, please notify the sender at Wipro or [EMAIL PROTECTED] immediately and destroy all copies of this message and any attachments. |
Confidentiality Notice The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain confidential or privileged information. If you are not the intended recipient, please notify the sender at Wipro or [EMAIL PROTECTED] immediately and destroy all copies of this message and any attachments. |
