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