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. |
