RE: xalan
> From: János Löbb [mailto:janos.l...@yale.edu] > Subject: Re: xalan > > [Deprecated] Xalan: org.apache.xalan.processor.TransformerFactoryImpl This message does NOT come from Tomcat (wrong format and content). Whether it's output by the JRE or a webapp is difficult to tell. I suspect the latter, possibly from some 3rd-party library. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: xalan
Hi Pid, Yes, I have, only this one: mysql-connector-java-5.1.12-bin.jar This is the newest of that kind. Thanks, János On May 7, 2010, at 12:26 PM, Pid wrote: > On 07/05/2010 16:18, János Löbb wrote: >> Hi, >> >> I see this in the catalina.out: >> . >> . >> May 6, 2010 4:17:30 PM org.apache.catalina.startup.Catalina start >> INFO: Server startup in 17970 ms >> [Deprecated] Xalan: org.apache.xalan.processor.TransformerFactoryImpl >> >> Is it normal ? What should I do to avoid it ? >> >> OS is OSX 10.6.2, with a latest java Apple provides with it. Tomcat is the >> 6.0.26 distribution. > > It doesn't report this on my Mac's Tomcat installation. > > Do you have extra JARs in tomcat/lib? > > > p > >> Thanks ahead, >> >> János >> - >> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >> For additional commands, e-mail: users-h...@tomcat.apache.org >> > > - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: xalan
On 07/05/2010 16:18, János Löbb wrote: > Hi, > > I see this in the catalina.out: > . > . > May 6, 2010 4:17:30 PM org.apache.catalina.startup.Catalina start > INFO: Server startup in 17970 ms > [Deprecated] Xalan: org.apache.xalan.processor.TransformerFactoryImpl > > Is it normal ? What should I do to avoid it ? > > OS is OSX 10.6.2, with a latest java Apple provides with it. Tomcat is the > 6.0.26 distribution. It doesn't report this on my Mac's Tomcat installation. Do you have extra JARs in tomcat/lib? p > Thanks ahead, > > János > - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > signature.asc Description: OpenPGP digital signature
RE: xalan
Consider it as a warning that this class can be removed in the next releases. Anyway, for the moment it should work without problems. For more information, see what version of xalan you are currently using and see the API documentation. -Original Message- From: János Löbb [mailto:janos.l...@yale.edu] Sent: 7. května 2010 17:19 [...] [Deprecated] Xalan: org.apache.xalan.processor.TransformerFactoryImpl Is it normal ? What should I do to avoid it ? [...] - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
xalan
Hi, I see this in the catalina.out: . . May 6, 2010 4:17:30 PM org.apache.catalina.startup.Catalina start INFO: Server startup in 17970 ms [Deprecated] Xalan: org.apache.xalan.processor.TransformerFactoryImpl Is it normal ? What should I do to avoid it ? OS is OSX 10.6.2, with a latest java Apple provides with it. Tomcat is the 6.0.26 distribution. Thanks ahead, János - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat Xalan classpath problem
On 06.11.2009 03:22, Benson Margulies wrote: > i don't suppose you've had time to look at the test case? Done, unfortunately worksforme :( - or should I write :) ? See https://issues.apache.org/bugzilla/show_bug.cgi?id=48116 What's next? Regards, Rainer P.S.: Are you at ApacheCon? > On Tue, Nov 3, 2009 at 9:22 AM, Rainer Jung wrote: > >> Just to make sure w.r.t. it being working in Jetty: You use the same >> Java version? Sun changed an important bit between Java 5 and Java 6, >> where they are now caching something detected during runtime in a global >> static thus partially breaking the dynamics of XML parser detection when >> using mutiple classloaders. The usual indication is a class cast >> exception, which is not the case in your situation, but nevertheless I >> wanted to check, whether there's a relation to Java 6 vs. Java 5 >> (handling in Java 6 is broken). >> >> Regards, >> >> Rainer >> >> On 03.11.2009 14:00, Benson Margulies wrote: >>> Here's the relevant log traffic of the missing method. I can get past >> this >>> problem by putting xalan into the endorsed directory, but I should not >> have >>> to do that when using the JAXP 1.4 API to create XPathFactory. >>> >>> >>> Caused by: java.lang.NoSuchMethodError: >>> org.apache.xpath.XPathContext.(Z)V >>> at org.apache.xpath.jaxp.XPathImpl.eval(XPathImpl.java:207) >>> at org.apache.xpath.jaxp.XPathImpl.evaluate(XPathImpl.java:281) >>> at >>> >> com.basistech.vws.env.GazetteerConfigManager.initialGazetteerConfiguration(GazetteerConfigManager.java:67) >>> at >>> >> com.basistech.vws.env.RLPEnvironmentManager.initialGazetteerConfiguration(RLPEnvironmentManager.java:400) >>> at >>> >> com.basistech.vws.env.RLPEnvironmentManager.initialConfiguration(RLPEnvironmentManager.java:358) >>> at >>> >> com.basistech.vws.env.RLPEnvironmentManager.initialize(RLPEnvironmentManager.java:182) >>> ... 48 more >>> org.apache.cxf.common.injection.ResourceInjector - method annotated by >>> @PostConstruct throws exception when invoked >>> java.lang.reflect.InvocationTargetException >>> >>> >>> On Tue, Nov 3, 2009 at 7:48 AM, André Warnier wrote: >>> >>>> Benson Margulies wrote: >>>> >>>>> I have a webapp that makes calls to the JAXP 1.4/Java 1.6 APIs that >> allow >>>>> the caller to pass in the class name of implementation classes. >>>>> >>>>> It all works find standalone. It works fine in Jetty. It fails in >> Tomcat >>>>> 6.0.20. The error is a missing method in a Xalan class; as if Tomcat >> has >>>>> somehow gotten an older version of Xalan into the classpath. >>>>> >>>>> I don't see any likely suspects in the Tomcat tree, so I'm momentarily >>>>> mystified. >>>>> >>>>> A piece of the logfile where the error messages occur may help someone >> to >>>> help you. >> >> - >> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >> For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat Xalan classpath problem
i don't suppose you've had time to look at the test case? On Tue, Nov 3, 2009 at 9:22 AM, Rainer Jung wrote: > Just to make sure w.r.t. it being working in Jetty: You use the same > Java version? Sun changed an important bit between Java 5 and Java 6, > where they are now caching something detected during runtime in a global > static thus partially breaking the dynamics of XML parser detection when > using mutiple classloaders. The usual indication is a class cast > exception, which is not the case in your situation, but nevertheless I > wanted to check, whether there's a relation to Java 6 vs. Java 5 > (handling in Java 6 is broken). > > Regards, > > Rainer > > On 03.11.2009 14:00, Benson Margulies wrote: > > Here's the relevant log traffic of the missing method. I can get past > this > > problem by putting xalan into the endorsed directory, but I should not > have > > to do that when using the JAXP 1.4 API to create XPathFactory. > > > > > > Caused by: java.lang.NoSuchMethodError: > > org.apache.xpath.XPathContext.(Z)V > > at org.apache.xpath.jaxp.XPathImpl.eval(XPathImpl.java:207) > > at org.apache.xpath.jaxp.XPathImpl.evaluate(XPathImpl.java:281) > > at > > > com.basistech.vws.env.GazetteerConfigManager.initialGazetteerConfiguration(GazetteerConfigManager.java:67) > > at > > > com.basistech.vws.env.RLPEnvironmentManager.initialGazetteerConfiguration(RLPEnvironmentManager.java:400) > > at > > > com.basistech.vws.env.RLPEnvironmentManager.initialConfiguration(RLPEnvironmentManager.java:358) > > at > > > com.basistech.vws.env.RLPEnvironmentManager.initialize(RLPEnvironmentManager.java:182) > > ... 48 more > > org.apache.cxf.common.injection.ResourceInjector - method annotated by > > @PostConstruct throws exception when invoked > > java.lang.reflect.InvocationTargetException > > > > > > On Tue, Nov 3, 2009 at 7:48 AM, André Warnier wrote: > > > >> Benson Margulies wrote: > >> > >>> I have a webapp that makes calls to the JAXP 1.4/Java 1.6 APIs that > allow > >>> the caller to pass in the class name of implementation classes. > >>> > >>> It all works find standalone. It works fine in Jetty. It fails in > Tomcat > >>> 6.0.20. The error is a missing method in a Xalan class; as if Tomcat > has > >>> somehow gotten an older version of Xalan into the classpath. > >>> > >>> I don't see any likely suspects in the Tomcat tree, so I'm momentarily > >>> mystified. > >>> > >>> A piece of the logfile where the error messages occur may help someone > to > >> help you. > > - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
Re: Tomcat Xalan classpath problem
I've attached a self-contained test case to bz 48116, so you can see this for yourself. On Tue, Nov 3, 2009 at 9:22 AM, Rainer Jung wrote: > Just to make sure w.r.t. it being working in Jetty: You use the same > Java version? Sun changed an important bit between Java 5 and Java 6, > where they are now caching something detected during runtime in a global > static thus partially breaking the dynamics of XML parser detection when > using mutiple classloaders. The usual indication is a class cast > exception, which is not the case in your situation, but nevertheless I > wanted to check, whether there's a relation to Java 6 vs. Java 5 > (handling in Java 6 is broken). > > Regards, > > Rainer > > On 03.11.2009 14:00, Benson Margulies wrote: > > Here's the relevant log traffic of the missing method. I can get past > this > > problem by putting xalan into the endorsed directory, but I should not > have > > to do that when using the JAXP 1.4 API to create XPathFactory. > > > > > > Caused by: java.lang.NoSuchMethodError: > > org.apache.xpath.XPathContext.(Z)V > > at org.apache.xpath.jaxp.XPathImpl.eval(XPathImpl.java:207) > > at org.apache.xpath.jaxp.XPathImpl.evaluate(XPathImpl.java:281) > > at > > > com.basistech.vws.env.GazetteerConfigManager.initialGazetteerConfiguration(GazetteerConfigManager.java:67) > > at > > > com.basistech.vws.env.RLPEnvironmentManager.initialGazetteerConfiguration(RLPEnvironmentManager.java:400) > > at > > > com.basistech.vws.env.RLPEnvironmentManager.initialConfiguration(RLPEnvironmentManager.java:358) > > at > > > com.basistech.vws.env.RLPEnvironmentManager.initialize(RLPEnvironmentManager.java:182) > > ... 48 more > > org.apache.cxf.common.injection.ResourceInjector - method annotated by > > @PostConstruct throws exception when invoked > > java.lang.reflect.InvocationTargetException > > > > > > On Tue, Nov 3, 2009 at 7:48 AM, André Warnier wrote: > > > >> Benson Margulies wrote: > >> > >>> I have a webapp that makes calls to the JAXP 1.4/Java 1.6 APIs that > allow > >>> the caller to pass in the class name of implementation classes. > >>> > >>> It all works find standalone. It works fine in Jetty. It fails in > Tomcat > >>> 6.0.20. The error is a missing method in a Xalan class; as if Tomcat > has > >>> somehow gotten an older version of Xalan into the classpath. > >>> > >>> I don't see any likely suspects in the Tomcat tree, so I'm momentarily > >>> mystified. > >>> > >>> A piece of the logfile where the error messages occur may help someone > to > >> help you. > > - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
Re: Tomcat Xalan classpath problem
I am sure that I'm using the MacOS JDK 1.6 at all points. Also, if you look closely at the below, you will see that the problem is that one part of Xalan is failing to call another part ... of Xalan. If I had JDK 1.5 I'd be missing the newInstance APIs that take the class name, and if I had other problems I'd have a mixture of sun. classes and org.apache. classes. But this is 100% org.apache. I shouldn't need to use endorsed at all with JDK 1.6, I claim, if I use the new newInstances APIs that take class names. But somehow Tomcat prevents that from working, I don't know how. On Tue, Nov 3, 2009 at 9:22 AM, Rainer Jung wrote: > Just to make sure w.r.t. it being working in Jetty: You use the same > Java version? Sun changed an important bit between Java 5 and Java 6, > where they are now caching something detected during runtime in a global > static thus partially breaking the dynamics of XML parser detection when > using mutiple classloaders. The usual indication is a class cast > exception, which is not the case in your situation, but nevertheless I > wanted to check, whether there's a relation to Java 6 vs. Java 5 > (handling in Java 6 is broken). > > Regards, > > Rainer > > On 03.11.2009 14:00, Benson Margulies wrote: > > Here's the relevant log traffic of the missing method. I can get past > this > > problem by putting xalan into the endorsed directory, but I should not > have > > to do that when using the JAXP 1.4 API to create XPathFactory. > > > > > > Caused by: java.lang.NoSuchMethodError: > > org.apache.xpath.XPathContext.(Z)V > > at org.apache.xpath.jaxp.XPathImpl.eval(XPathImpl.java:207) > > at org.apache.xpath.jaxp.XPathImpl.evaluate(XPathImpl.java:281) > > at > > > com.basistech.vws.env.GazetteerConfigManager.initialGazetteerConfiguration(GazetteerConfigManager.java:67) > > at > > > com.basistech.vws.env.RLPEnvironmentManager.initialGazetteerConfiguration(RLPEnvironmentManager.java:400) > > at > > > com.basistech.vws.env.RLPEnvironmentManager.initialConfiguration(RLPEnvironmentManager.java:358) > > at > > > com.basistech.vws.env.RLPEnvironmentManager.initialize(RLPEnvironmentManager.java:182) > > ... 48 more > > org.apache.cxf.common.injection.ResourceInjector - method annotated by > > @PostConstruct throws exception when invoked > > java.lang.reflect.InvocationTargetException > > > > > > On Tue, Nov 3, 2009 at 7:48 AM, André Warnier wrote: > > > >> Benson Margulies wrote: > >> > >>> I have a webapp that makes calls to the JAXP 1.4/Java 1.6 APIs that > allow > >>> the caller to pass in the class name of implementation classes. > >>> > >>> It all works find standalone. It works fine in Jetty. It fails in > Tomcat > >>> 6.0.20. The error is a missing method in a Xalan class; as if Tomcat > has > >>> somehow gotten an older version of Xalan into the classpath. > >>> > >>> I don't see any likely suspects in the Tomcat tree, so I'm momentarily > >>> mystified. > >>> > >>> A piece of the logfile where the error messages occur may help someone > to > >> help you. > > - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
Re: Tomcat Xalan classpath problem
Just to make sure w.r.t. it being working in Jetty: You use the same Java version? Sun changed an important bit between Java 5 and Java 6, where they are now caching something detected during runtime in a global static thus partially breaking the dynamics of XML parser detection when using mutiple classloaders. The usual indication is a class cast exception, which is not the case in your situation, but nevertheless I wanted to check, whether there's a relation to Java 6 vs. Java 5 (handling in Java 6 is broken). Regards, Rainer On 03.11.2009 14:00, Benson Margulies wrote: > Here's the relevant log traffic of the missing method. I can get past this > problem by putting xalan into the endorsed directory, but I should not have > to do that when using the JAXP 1.4 API to create XPathFactory. > > > Caused by: java.lang.NoSuchMethodError: > org.apache.xpath.XPathContext.(Z)V > at org.apache.xpath.jaxp.XPathImpl.eval(XPathImpl.java:207) > at org.apache.xpath.jaxp.XPathImpl.evaluate(XPathImpl.java:281) > at > com.basistech.vws.env.GazetteerConfigManager.initialGazetteerConfiguration(GazetteerConfigManager.java:67) > at > com.basistech.vws.env.RLPEnvironmentManager.initialGazetteerConfiguration(RLPEnvironmentManager.java:400) > at > com.basistech.vws.env.RLPEnvironmentManager.initialConfiguration(RLPEnvironmentManager.java:358) > at > com.basistech.vws.env.RLPEnvironmentManager.initialize(RLPEnvironmentManager.java:182) > ... 48 more > org.apache.cxf.common.injection.ResourceInjector - method annotated by > @PostConstruct throws exception when invoked > java.lang.reflect.InvocationTargetException > > > On Tue, Nov 3, 2009 at 7:48 AM, André Warnier wrote: > >> Benson Margulies wrote: >> >>> I have a webapp that makes calls to the JAXP 1.4/Java 1.6 APIs that allow >>> the caller to pass in the class name of implementation classes. >>> >>> It all works find standalone. It works fine in Jetty. It fails in Tomcat >>> 6.0.20. The error is a missing method in a Xalan class; as if Tomcat has >>> somehow gotten an older version of Xalan into the classpath. >>> >>> I don't see any likely suspects in the Tomcat tree, so I'm momentarily >>> mystified. >>> >>> A piece of the logfile where the error messages occur may help someone to >> help you. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat Xalan classpath problem
Here's the relevant log traffic of the missing method. I can get past this problem by putting xalan into the endorsed directory, but I should not have to do that when using the JAXP 1.4 API to create XPathFactory. Caused by: java.lang.NoSuchMethodError: org.apache.xpath.XPathContext.(Z)V at org.apache.xpath.jaxp.XPathImpl.eval(XPathImpl.java:207) at org.apache.xpath.jaxp.XPathImpl.evaluate(XPathImpl.java:281) at com.basistech.vws.env.GazetteerConfigManager.initialGazetteerConfiguration(GazetteerConfigManager.java:67) at com.basistech.vws.env.RLPEnvironmentManager.initialGazetteerConfiguration(RLPEnvironmentManager.java:400) at com.basistech.vws.env.RLPEnvironmentManager.initialConfiguration(RLPEnvironmentManager.java:358) at com.basistech.vws.env.RLPEnvironmentManager.initialize(RLPEnvironmentManager.java:182) ... 48 more org.apache.cxf.common.injection.ResourceInjector - method annotated by @PostConstruct throws exception when invoked java.lang.reflect.InvocationTargetException On Tue, Nov 3, 2009 at 7:48 AM, André Warnier wrote: > Benson Margulies wrote: > >> I have a webapp that makes calls to the JAXP 1.4/Java 1.6 APIs that allow >> the caller to pass in the class name of implementation classes. >> >> It all works find standalone. It works fine in Jetty. It fails in Tomcat >> 6.0.20. The error is a missing method in a Xalan class; as if Tomcat has >> somehow gotten an older version of Xalan into the classpath. >> >> I don't see any likely suspects in the Tomcat tree, so I'm momentarily >> mystified. >> >> A piece of the logfile where the error messages occur may help someone to > help you. > > > - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
Re: Tomcat Xalan classpath problem
Benson Margulies wrote: I have a webapp that makes calls to the JAXP 1.4/Java 1.6 APIs that allow the caller to pass in the class name of implementation classes. It all works find standalone. It works fine in Jetty. It fails in Tomcat 6.0.20. The error is a missing method in a Xalan class; as if Tomcat has somehow gotten an older version of Xalan into the classpath. I don't see any likely suspects in the Tomcat tree, so I'm momentarily mystified. A piece of the logfile where the error messages occur may help someone to help you. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Tomcat Xalan classpath problem
I have a webapp that makes calls to the JAXP 1.4/Java 1.6 APIs that allow the caller to pass in the class name of implementation classes. It all works find standalone. It works fine in Jetty. It fails in Tomcat 6.0.20. The error is a missing method in a Xalan class; as if Tomcat has somehow gotten an older version of Xalan into the classpath. I don't see any likely suspects in the Tomcat tree, so I'm momentarily mystified.
Re: Run Xalan on Tomcat
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Rashmi, Rashmi Rubdi wrote: > On 5/14/07, Christopher Schultz <[EMAIL PROTECTED]> wrote: >> Rashmi Rubdi wrote: >> > One way to use Xalan is with JSTL XML tags inside a JSP. >> >> A much better way is to use Cocoon (http://cocoon.apache.org). > > I've not tried Cocoon yet, so I really cant compare JSTL XML tags with > Cocoon but I know that with JSTL XML tags you only need 3 lines of > code to transform an XML with an XSLT file, and show the output on a > JSP --- and it requires Xalan JAR files. Cocoon requires no JSP at all, is configured entirely using XML, and comes with all required libraries. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGSaYm9CaO5/Lv0PARAvJdAJ9+/n6eTIh3gn6qzPyN8BzNQmPtWQCfVFvh Uu5EQCJCSBjac9X1+nBWYdE= =FHFl -END PGP SIGNATURE- - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Run Xalan on Tomcat
On 5/14/07, Christopher Schultz <[EMAIL PROTECTED]> wrote: Rashmi Rubdi wrote: > One way to use Xalan is with JSTL XML tags inside a JSP. A much better way is to use Cocoon (http://cocoon.apache.org). I've not tried Cocoon yet, so I really cant compare JSTL XML tags with Cocoon but I know that with JSTL XML tags you only need 3 lines of code to transform an XML with an XSLT file, and show the output on a JSP --- and it requires Xalan JAR files. 3 lines are 1) Import XML 2) Import XSLT 3) x:transform xml with xslt Well other than the above, it is also possible transform within a JSP with x:parse tag. In addition to Cocoon, JSTL XML tags, I think there are other frameworks also available by Apache , each framework serves it's own purpose. - -chris -Regards Rashmi - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Run Xalan on Tomcat
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Rashmi, Rashmi Rubdi wrote: > One way to use Xalan is with JSTL XML tags inside a JSP. A much better way is to use Cocoon (http://cocoon.apache.org). - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGSFqO9CaO5/Lv0PARAgB8AJ0R9oWPKwRn/Tkw+7uYL1qe2oarxQCgwN8x GDeY006V0HDO1sUba3QSsGs= =u6q9 -END PGP SIGNATURE- - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Run Xalan on Tomcat
Domenico download xalan here http://xml.apache.org/xalan-j/downloads.html I would deploy the demo servlet xalanservlet suppling the 3 required params on the QueryString XML XSL PVAL e.g. http://localhost:8080/xalanservlet/?XML=fooparam.xml&XSL=fooparam.xsl&PVAL=Hello HTH/ Martin This email message and any files transmitted with it contain confidential information intended only for the person(s) to whom this email message is addressed. If you have received this email message in error, please notify the sender immediately by telephone or email and destroy the original message without making a copy. Thank you. - Original Message - From: "domenico di leo" <[EMAIL PROTECTED]> To: Sent: Sunday, May 13, 2007 4:49 PM Subject: Run Xalan on Tomcat Hi How can I run Xalan on Tomcat? I use Tomcat 5.5.23 and I'm newbie many thanks - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Run Xalan on Tomcat
On 5/13/07, domenico di leo <[EMAIL PROTECTED]> wrote: Hi How can I run Xalan on Tomcat? Configure it as you would configure other plug-ins. That is, place xalan.jar (and dependent JAR files such as serializer.jar) either in 1) your projects /WEB-INF/lib folder or in Tomcat's shared folder (your choice). I use Tomcat 5.5.23 and I'm newbie How do you plan to use Xalan on Tomcat? One way to use Xalan is with JSTL XML tags inside a JSP. many thanks -Regards Rashmi - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Run Xalan on Tomcat
Hi How can I run Xalan on Tomcat? I use Tomcat 5.5.23 and I'm newbie many thanks - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Tomcat 5.5 problem with JRE 1.5 (Xalan and jstl 1.1 problem with transformer)
Hello everyone, I hope someone in this list can help me with this. I developed a simple XML based document repository using JSTL xml tags 1.0 under Tomcat 4.0. Now I am trying to do the same with Tomcat 5.5.12 using JSTL 1.1 but I keep receiving an error message about the instantiation of the transformer: javax.xml.transform.TransformerFactoryConfigurationError: Provider org.apache.xalan.transformer.TransformerImpl could not be instantiated: java.lang.InstantiationException: org.apache.xalan.transformer.TransformerImpl This is my test environment: - Windows XP - JRE 1.5.0 - Tomcat 5.5.12 - A CMS compliant with Tomcat 5 and coming with JSTL 1.1 libraries (InfoGlue: www.infoglue.org) I see JRE 1.5.0 contains an internal version of xalan and xerces and apparently I cannot override them. I did the following to overcome the problem: - download the latest versions of xalan.jar, xercesImpl.jar and xml-apis.jar and place them under the WEB-inf directory of my application - place the same files under [TOMCAT_HOME]/common/endorsed - place the same files under [JAVA_HOME]/lib/endorsed This is my very simple transformer page (very very basic): <%@ taglib uri="http://java.sun.com/jsp/jstl/core"; prefix="c" %> <%@ taglib uri="http://java.sun.com/jsp/jstl/xml"; prefix="x" %> The request-scoped variables contain what they should (I tested them importing directly to the page without storing the imported contents in variables). I really don't know what else to try. Thank you to those who had the patience to read and to those who will be so kind to reply... Valeria
