RE: Re: [Mav-user] Maverick in Tomcat 3.3 using JSP
Oops :-) Amusingly enough, this problem was fixed last week during some refactoring. The current CVS copy of Maverick should only instantiate jaxp TransformerFactory objects when they are actually used... but then I said this before :-) When I get more documentation written I'll release another beta. As far as Tomcat 3.3 goes, I vaguely recall that it has some strange classloader issues and it's very sensitive to where you put the xalan.jar. I've never spent any serious time using Tomcat v3, so I'm not sure I can be much help beyond this. Jeff Schnitzer [EMAIL PROTECTED] > -Original Message- > From: Gerald de Jong [mailto:[EMAIL PROTECTED]] > Sent: Friday, January 25, 2002 4:25 AM > To: [EMAIL PROTECTED] > Subject: Re: Re: [Mav-user] Maverick in Tomcat 3.3 using JSP > > On Friday 25 January 2002 09:50, Jeff Schnitzer wrote: > > > i'll move to v2, but why would i need an xslt processor if i'm using > > no > > > xslt? > > > > Because of a very silly piece of code that was long ago corrected in > > Maverick 2.0 :-) If you're not using xslt, you could just comment out > > ConfigLoader.java line 312 and everything will be fine (note you'll > > still need to declare the variable, just initialize it to null). > > > > Sorry about that. There really isn't any good reason. If switching to > > Maverick 2.0 is not an option, and putting a processor on the classpath > > (any processor will do) is problematic, I can send you a special build. > > > > Incidentally, even in Maverick 2.0, it is still possible to need an xslt > > processor even if you aren't using xslt. Maverick uses JAXP if it ever > > needs to serialize a DOM tree. This is pretty unlikely if you're not > > using xslt, but it could happen :-) > > > > Jeff Schnitzer > > [EMAIL PROTECTED] > > thanks a lot for your responsiveness, Jeff! > > i've moved to maverick 2.0, and i've put xalan.jar in the classpath, but > strangely enough it doesn't seem to think that it's there! it works (of > course) in Tomcat 4, but in the Tomcat 3.2 i'm using it doesn't. > > it should find org.apache.xalan.processor.TransformerFactoryImpl, but it > doesn't. any idea why? here's the stacktrace: > > [Loader] Loading config from > /opt/JBoss-2.4.3_Tomcat- > 3.2.3/jboss/tmp/deploy/Default/avv.ear/web1001/WEB-INF/maverick.xml > [MasterTransformFactory] Transform factory for "document" is > org.infohazard.maverick.transform.DocumentTransformFactory > [MasterTransformFactory] Transform factory for "xslt" is > org.infohazard.maverick.transform.XSLTransformFactory > [MasterViewFactory] View factory for "redirect" is > org.infohazard.maverick.view.RedirectViewFactory > [J2EE Deployer Default] Starting avv.war failed! > [Default] javax.xml.transform.TransformerFactoryConfigurationError: > java.lang.ClassNotFoundException: > org.apache.xalan.processor.TransformerFactoryImpl > [Default] at > javax.xml.transform.TransformerFactory.newInstance(TransformerFactory.ja va > :121) > [Default] > [Default] at > org.infohazard.maverick.transform.NonTransform.(NonTransform.jav a: > 23) > [Default] > [Default] at > org.infohazard.maverick.view.TrivialViewFactory.(TrivialViewFactor y. > java:20) > [Default] > [Default] at > org.infohazard.maverick.flow.Loader.setupCoreModules(Loader.java:137) > [Default] > [Default] at > org.infohazard.maverick.flow.Loader.init(Loader.java:114) > [Default] > [Default] at > org.infohazard.maverick.flow.Loader.(Loader.java:90) > [Default] > [Default] at > org.infohazard.maverick.Dispatcher.reloadConfig(Dispatcher.java:149) > [Default] > [Default] at > org.infohazard.maverick.Dispatcher.init(Dispatcher.java:86) > [Default] > > > -- > Beautiful Code BV > Rotterdam, The Netherlands > http://www.beautifulcode.nl > > ___ > Mav-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/mav-user ___ Mav-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/mav-user
Re: Re: [Mav-user] Maverick in Tomcat 3.3 using JSP
On Friday 25 January 2002 09:50, Jeff Schnitzer wrote: > > i'll move to v2, but why would i need an xslt processor if i'm using > no > > xslt? > > Because of a very silly piece of code that was long ago corrected in > Maverick 2.0 :-) If you're not using xslt, you could just comment out > ConfigLoader.java line 312 and everything will be fine (note you'll > still need to declare the variable, just initialize it to null). > > Sorry about that. There really isn't any good reason. If switching to > Maverick 2.0 is not an option, and putting a processor on the classpath > (any processor will do) is problematic, I can send you a special build. > > Incidentally, even in Maverick 2.0, it is still possible to need an xslt > processor even if you aren't using xslt. Maverick uses JAXP if it ever > needs to serialize a DOM tree. This is pretty unlikely if you're not > using xslt, but it could happen :-) > > Jeff Schnitzer > [EMAIL PROTECTED] thanks a lot for your responsiveness, Jeff! i've moved to maverick 2.0, and i've put xalan.jar in the classpath, but strangely enough it doesn't seem to think that it's there! it works (of course) in Tomcat 4, but in the Tomcat 3.2 i'm using it doesn't. it should find org.apache.xalan.processor.TransformerFactoryImpl, but it doesn't. any idea why? here's the stacktrace: [Loader] Loading config from /opt/JBoss-2.4.3_Tomcat-3.2.3/jboss/tmp/deploy/Default/avv.ear/web1001/WEB-INF/maverick.xml [MasterTransformFactory] Transform factory for "document" is org.infohazard.maverick.transform.DocumentTransformFactory [MasterTransformFactory] Transform factory for "xslt" is org.infohazard.maverick.transform.XSLTransformFactory [MasterViewFactory] View factory for "redirect" is org.infohazard.maverick.view.RedirectViewFactory [J2EE Deployer Default] Starting avv.war failed! [Default] javax.xml.transform.TransformerFactoryConfigurationError: java.lang.ClassNotFoundException: org.apache.xalan.processor.TransformerFactoryImpl [Default] at javax.xml.transform.TransformerFactory.newInstance(TransformerFactory.java:121) [Default] [Default] at org.infohazard.maverick.transform.NonTransform.(NonTransform.java:23) [Default] [Default] at org.infohazard.maverick.view.TrivialViewFactory.(TrivialViewFactory.java:20) [Default] [Default] at org.infohazard.maverick.flow.Loader.setupCoreModules(Loader.java:137) [Default] [Default] at org.infohazard.maverick.flow.Loader.init(Loader.java:114) [Default] [Default] at org.infohazard.maverick.flow.Loader.(Loader.java:90) [Default] [Default] at org.infohazard.maverick.Dispatcher.reloadConfig(Dispatcher.java:149) [Default] [Default] at org.infohazard.maverick.Dispatcher.init(Dispatcher.java:86) [Default] -- Beautiful Code BV Rotterdam, The Netherlands http://www.beautifulcode.nl ___ Mav-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/mav-user
RE: Re: [Mav-user] Maverick in Tomcat 3.3 using JSP
> From: Gerald de Jong [mailto:[EMAIL PROTECTED]] > > hi Jeff, > > do you see a transformation pipeline? > > > > > > > > > > > i'll move to v2, but why would i need an xslt processor if i'm using no > xslt? Because of a very silly piece of code that was long ago corrected in Maverick 2.0 :-) If you're not using xslt, you could just comment out ConfigLoader.java line 312 and everything will be fine (note you'll still need to declare the variable, just initialize it to null). Sorry about that. There really isn't any good reason. If switching to Maverick 2.0 is not an option, and putting a processor on the classpath (any processor will do) is problematic, I can send you a special build. Incidentally, even in Maverick 2.0, it is still possible to need an xslt processor even if you aren't using xslt. Maverick uses JAXP if it ever needs to serialize a DOM tree. This is pretty unlikely if you're not using xslt, but it could happen :-) Jeff Schnitzer [EMAIL PROTECTED] ___ Mav-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/mav-user
Fwd: Re: [Mav-user] Maverick in Tomcat 3.3 using JSP
hi Jeff, do you see a transformation pipeline? i'll move to v2, but why would i need an xslt processor if i'm using no xslt? On Friday 25 January 2002 00:00, Jeff Schnitzer wrote: > The answer to "should I move to Maverick v2" is "yes, if you can live > with the documentation" :-) I have no idea offhand how much (if any) of > it will work with Tomcat v3, though. > > The immediate problem appears to be that you do not have a > jaxp-compliant xslt processor on the classpath, and you have configured > a view with a transformation pipeline. > > Xalan 2.1 is known to work well; > just drop it in your tomcat/lib directory. Note that the Xalan 2.2.0 > release has not been tested with Maverick v1, but the developer releases > definitely had problems, so I would recommend sticking with 2.1 until > you're ready for Maverick 2.0. > > The problem with the Servlet 2.2 API is that it does not support > HttpServletResponseWrapper, so there is no way to "capture" the output > of JSP pages or static documents and run them through transforms. As > long as you don't try to do this, Maverick (v1) _should_ work just fine. > Regular domify views should be ok. Note that the friendbook-domify > example not only runs transforms on static documents, but makes a call > to HttpServletRequest.getParameterMap(), which was introduced with the > Servlet 2.3 API. The sample definitely won't work on Tomcat 3.x. > > Good luck, > Jeff Schnitzer > [EMAIL PROTECTED] > > > -Original Message----- > > From: Gerald de Jong [mailto:[EMAIL PROTECTED]] > > Sent: Friday, January 25, 2002 12:04 AM > > To: Jeff Schnitzer > > Subject: Re: [Mav-user] Maverick in Tomcat 3.3 using JSP > > > > here's the stack trace. i'm using maverick v1. should i move to 2? > > > > javax.xml.transform.TransformerFactoryConfigurationError: > > java.lang.ClassNotFoundException: > > org.apache.xalan.processor.TransformerFactoryImpl > > > javax.xml.transform.TransformerFactory.newInstance(TransformerFactory.ja > va > > :121) > > > org.infohazard.maverick.flow.PipelineTransforming.(PipelineTransfo > rm > > ing.java:25) > > > org.infohazard.maverick.util.ConfigLoader.extractPipeline(ConfigLoader.j > av > > a:442) > > > org.infohazard.maverick.util.ConfigLoader.newView(ConfigLoader.java:312) > > > org.infohazard.maverick.util.ConfigLoader.newCommand(ConfigLoader.java:4 > 23 > > ) > > > org.infohazard.maverick.util.ConfigLoader.loadConfig(ConfigLoader.java:1 > 96 > > ) > > > org.infohazard.maverick.util.ConfigLoader.initialize(ConfigLoader.java:1 > 67 > > ) > > > org.infohazard.maverick.util.ConfigLoader.(ConfigLoader.java:132) > > org.infohazard.maverick.Dispatcher.reloadConfig(Dispatcher.java:129) > > at org.infohazard.maverick.Dispatcher.init(Dispatcher.java:76) > > > > > > On Thursday 24 January 2002 23:38, Jeff Schnitzer wrote: > > > What was the stack trace? I would expect that the class not found > was > > > HttpServletResponseWrapper, but if you're not using XSLT, I am > surprised > > > that it would come up. > > > > > > Is this with maverick v1 or v2? > > > > > > Jeff > > > > > > > -Original Message- > > > > From: Gerald de Jong [mailto:[EMAIL PROTECTED]] > > > > Sent: Thursday, January 24, 2002 11:32 AM > > > > To: [EMAIL PROTECTED] > > > > Subject: [Mav-user] Maverick in Tomcat 3.3 using JSP > > > > > > > > in the FAQ it says that the only reason Maverick needs the Servlet > 2.3 > > > API > > > > is > > > > for the pipelining (i assume this is for XSLT). > > > > > > > > is pipelining needed for JSPs as well? i tried but was unable to > get > > > > Maverick working at all in Tomcat 3.3, because it had a > > > class-not-found > > > > for > > > > something related to pipelining. > > > > > > > > is anyone using Maverick in pre-2.3 servlet engines? > > > > > > > > -- > > > > Beautiful Code BV > > > > Rotterdam, The Netherlands > > > > http://www.beautifulcode.nl -- Beautiful Code BV Rotterdam, The Netherlands http://www.beautifulcode.nl ___ Mav-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/mav-user
RE: [Mav-user] Maverick in Tomcat 3.3 using JSP
The answer to "should I move to Maverick v2" is "yes, if you can live with the documentation" :-) I have no idea offhand how much (if any) of it will work with Tomcat v3, though. The immediate problem appears to be that you do not have a jaxp-compliant xslt processor on the classpath, and you have configured a view with a transformation pipeline. Xalan 2.1 is known to work well; just drop it in your tomcat/lib directory. Note that the Xalan 2.2.0 release has not been tested with Maverick v1, but the developer releases definitely had problems, so I would recommend sticking with 2.1 until you're ready for Maverick 2.0. The problem with the Servlet 2.2 API is that it does not support HttpServletResponseWrapper, so there is no way to "capture" the output of JSP pages or static documents and run them through transforms. As long as you don't try to do this, Maverick (v1) _should_ work just fine. Regular domify views should be ok. Note that the friendbook-domify example not only runs transforms on static documents, but makes a call to HttpServletRequest.getParameterMap(), which was introduced with the Servlet 2.3 API. The sample definitely won't work on Tomcat 3.x. Good luck, Jeff Schnitzer [EMAIL PROTECTED] > -Original Message- > From: Gerald de Jong [mailto:[EMAIL PROTECTED]] > Sent: Friday, January 25, 2002 12:04 AM > To: Jeff Schnitzer > Subject: Re: [Mav-user] Maverick in Tomcat 3.3 using JSP > > here's the stack trace. i'm using maverick v1. should i move to 2? > > javax.xml.transform.TransformerFactoryConfigurationError: > java.lang.ClassNotFoundException: > org.apache.xalan.processor.TransformerFactoryImpl > javax.xml.transform.TransformerFactory.newInstance(TransformerFactory.ja va > :121) > org.infohazard.maverick.flow.PipelineTransforming.(PipelineTransfo rm > ing.java:25) > org.infohazard.maverick.util.ConfigLoader.extractPipeline(ConfigLoader.j av > a:442) > org.infohazard.maverick.util.ConfigLoader.newView(ConfigLoader.java:312) > org.infohazard.maverick.util.ConfigLoader.newCommand(ConfigLoader.java:4 23 > ) > org.infohazard.maverick.util.ConfigLoader.loadConfig(ConfigLoader.java:1 96 > ) > org.infohazard.maverick.util.ConfigLoader.initialize(ConfigLoader.java:1 67 > ) > org.infohazard.maverick.util.ConfigLoader.(ConfigLoader.java:132) > org.infohazard.maverick.Dispatcher.reloadConfig(Dispatcher.java:129) > at org.infohazard.maverick.Dispatcher.init(Dispatcher.java:76) > > > On Thursday 24 January 2002 23:38, Jeff Schnitzer wrote: > > What was the stack trace? I would expect that the class not found was > > HttpServletResponseWrapper, but if you're not using XSLT, I am surprised > > that it would come up. > > > > Is this with maverick v1 or v2? > > > > Jeff > > > > > -Original Message- > > > From: Gerald de Jong [mailto:[EMAIL PROTECTED]] > > > Sent: Thursday, January 24, 2002 11:32 AM > > > To: [EMAIL PROTECTED] > > > Subject: [Mav-user] Maverick in Tomcat 3.3 using JSP > > > > > > in the FAQ it says that the only reason Maverick needs the Servlet 2.3 > > API > > > is > > > for the pipelining (i assume this is for XSLT). > > > > > > is pipelining needed for JSPs as well? i tried but was unable to get > > > Maverick working at all in Tomcat 3.3, because it had a > > class-not-found > > > for > > > something related to pipelining. > > > > > > is anyone using Maverick in pre-2.3 servlet engines? > > > > > > -- > > > Beautiful Code BV > > > Rotterdam, The Netherlands > > > http://www.beautifulcode.nl > > > > > > ___ > > > Mav-user mailing list > > > [EMAIL PROTECTED] > > > https://lists.sourceforge.net/lists/listinfo/mav-user > > > > ___ > > Mav-user mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/mav-user > > > > > > -- > Beautiful Code BV > Rotterdam, The Netherlands > http://www.beautifulcode.nl ___ Mav-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/mav-user
RE: [Mav-user] Maverick in Tomcat 3.3 using JSP
What was the stack trace? I would expect that the class not found was HttpServletResponseWrapper, but if you're not using XSLT, I am surprised that it would come up. Is this with maverick v1 or v2? Jeff > -Original Message- > From: Gerald de Jong [mailto:[EMAIL PROTECTED]] > Sent: Thursday, January 24, 2002 11:32 AM > To: [EMAIL PROTECTED] > Subject: [Mav-user] Maverick in Tomcat 3.3 using JSP > > in the FAQ it says that the only reason Maverick needs the Servlet 2.3 API > is > for the pipelining (i assume this is for XSLT). > > is pipelining needed for JSPs as well? i tried but was unable to get > Maverick working at all in Tomcat 3.3, because it had a class-not-found > for > something related to pipelining. > > is anyone using Maverick in pre-2.3 servlet engines? > > -- > Beautiful Code BV > Rotterdam, The Netherlands > http://www.beautifulcode.nl > > ___ > Mav-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/mav-user ___ Mav-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/mav-user
