Reza,

Can you move the Xalan.jar file from the endorsed directory to the lib directory
in your Web Application. I am wondering if it is possible that SUN repackaged
the Xalan code so that it could exist as in the JVM (rt.jar) and still be included
as part of the class path. The endorsed directory just puts the jar in the class path
before rt.jar (i.e. the boot classpath) so if some of the endorsed restrictions were
lifted, leaving the jar file in the endorsed dir would work just as well as putting it
in the real classpath.


Thanks
John G


Reza Ferrydiansyah wrote:

Yep that did the trick.
Downloaded the xalan. And put the xalan.jar file into that directory
made it work

Thanks.....

On Tue, 7 Sep 2004 16:31:50 -0400, Shapira, Yoav <[EMAIL PROTECTED]> wrote:


Hi,
As the release notes say, the first thing to try if you are
experimenting Xalan problems is to take the latest stable version of
Xalan and put it in the $CATALINA_HOME/common/endorsed directory.  Give
that a shot and let us know how it goes ;)

Yoav Shapira
Millennium Research Informatics






-----Original Message-----
From: Reza Ferrydiansyah [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 07, 2004 4:25 PM
To: [EMAIL PROTECTED]
Subject: Xalan problem :(

Hi all,

I'm using jdk1.5rc with tomcat 5.0.27 on windows 2003 server

This line from one of my classes (inside
WEB-INF/classes/myPackage/myClass.java) gives me an error as follows:
TransformerFactory tFactory = TransformerFactory.newInstance();

javax.xml.transform.TransformerFactoryConfigurationError: Provider
org.apache.xalan.processor.TransformerFactoryImpl not found
javax.xml.transform.TransformerFactory.newInstance(Unknown


Source)


I have the source of the jdk1.5rc and looking at the source
org.apache.xalan.processor.TransformerFactoryImpl does not exist. (to
be exact it is com.sun.org.apache.xalan... )

Looking at the TransformerFactory newInstance method I can't help to
notice that they try to look for

public static TransformerFactory newInstance()
      throws TransformerFactoryConfigurationError {
      try {
          return (TransformerFactory) FactoryFinder.find(
          /* The default property name according to the JAXP spec */
          "javax.xml.transform.TransformerFactory",
          /* The fallback implementation class name, XSLTC */

"com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl");

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^


^^^^


^^^^^
      } catch (FactoryFinder.ConfigurationError e) {

which makes me believe that xalan has been changed for jdk1.5rc? Is


that


right?

So I did a little experiment. I created a java program which all it
does is create a newInstance of the TransformerFactory. That is its
main function consists of :
TransformerFactory tFactory = TransformerFactory.newInstance();

Compiled it with jdk1.5rc, executed it and it works fine. So the
question is why does the program work when I execute it via command
line (using javac, and java) but not with the tomcat. Tomcat should
use the same library as the one in java right? Of course the biggest
question is how do I make my program work...

Additional information. This program is done in a new server. That is
there is no previous versions of the jdk nor previous version of
tomcat.

Thank you.

--
--
Reza Ferrydiansyah
http://www.informatika.org/~reza

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


This e-mail, including any attachments, is a confidential business communication, and 
may contain information that is confidential, proprietary and/or privileged.  This 
e-mail is intended only for the individual(s) to whom it is addressed, and may not be 
saved, copied, printed, disclosed or used by anyone else.  If you are not the(an) 
intended recipient, please immediately delete this e-mail from your computer system 
and notify the sender.  Thank you.












--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to