RE: Reason of HTMLSerializer exception

2003-01-10 Thread Giacomo Pati
On Fri, 10 Jan 2003, Stephan Michels wrote: > > > > On Fri, 10 Jan 2003, Carsten Ziegeler wrote: > > > > -Original Message- > > > From: Stephan Michels [mailto:[EMAIL PROTECTED]] > > > > > > Strange .. Without these libs in WEB-INF/lib/ I don't get this > > > exception, and with I got this

RE: Reason of HTMLSerializer exception

2003-01-10 Thread Geoff Howard
> > I'm using tomcat 3.3.1 - remember, if you're using tomcat 4.x > > you have to copy the cocoon/lib/endorsed jars to tomcat's > > common/endorsed directory as Giacomo asked. > > Okay okay, to repeat (I'm a bit slow today): > > lib/core -> cocoon/WEB-INF/lib > lib/optional -> cocoon/WEB-INF/lib

RE: Reason of HTMLSerializer exception

2003-01-10 Thread Stephan Michels
On Fri, 10 Jan 2003, Carsten Ziegeler wrote: > > -Original Message- > > From: Stephan Michels [mailto:[EMAIL PROTECTED]] > > > > Strange .. Without these libs in WEB-INF/lib/ I don't get this > > exception, and with I got this exception. Hmm. > > > > Do you use tomcat? And when yes, whi

Re: Reason of HTMLSerializer exception

2003-01-10 Thread Giacomo Pati
On Fri, 10 Jan 2003, Stephan Michels wrote: > > > > On Fri, 10 Jan 2003, Giacomo Pati wrote: > > > On Fri, 10 Jan 2003, Stephan Michels wrote: > > > > > > > > Hi, > > > > > > if I start the Cocoon webapp into tomcat I got always this exception. > > > > > > org.apache.cocoon.CascadingIOException: >

RE: Reason of HTMLSerializer exception

2003-01-10 Thread Giacomo Pati
On Fri, 10 Jan 2003, Carsten Ziegeler wrote: > > -Original Message- > > From: Stephan Michels [mailto:[EMAIL PROTECTED]] > > > > Strange .. Without these libs in WEB-INF/lib/ I don't get this > > exception, and with I got this exception. Hmm. > > > > Do you use tomcat? And when yes, which

Re: Reason of HTMLSerializer exception

2003-01-10 Thread Stephan Michels
On Fri, 10 Jan 2003, Giacomo Pati wrote: > On Fri, 10 Jan 2003, Stephan Michels wrote: > > > > > Hi, > > > > if I start the Cocoon webapp into tomcat I got always this exception. > > > > org.apache.cocoon.CascadingIOException: > > org.apache.xml.utils.WrappedRuntimeException: The output format

RE: Reason of HTMLSerializer exception

2003-01-10 Thread Carsten Ziegeler
> -Original Message- > From: Stephan Michels [mailto:[EMAIL PROTECTED]] > > Strange .. Without these libs in WEB-INF/lib/ I don't get this > exception, and with I got this exception. Hmm. > > Do you use tomcat? And when yes, which version? > I'm using tomcat 3.3.1 - remember, if you're u

RE: Reason of HTMLSerializer exception

2003-01-10 Thread Stephan Michels
On Fri, 10 Jan 2003, Carsten Ziegeler wrote: > > > > -Original Message- > > From: Stephan Michels [mailto:[EMAIL PROTECTED]] > > > > On Fri, 10 Jan 2003, Carsten Ziegeler wrote: > > > > > We had this problem, when not the proper version of xalan was in the > > > classpath or precisly in

Re: Reason of HTMLSerializer exception

2003-01-10 Thread Giacomo Pati
On Fri, 10 Jan 2003, Stephan Michels wrote: > > Hi, > > if I start the Cocoon webapp into tomcat I got always this exception. > > org.apache.cocoon.CascadingIOException: > org.apache.xml.utils.WrappedRuntimeException: The output format must have > a '{http://xml.apache.org/xslt}content-handler' pr

RE: Reason of HTMLSerializer exception

2003-01-10 Thread Carsten Ziegeler
> -Original Message- > From: Stephan Michels [mailto:[EMAIL PROTECTED]] > > On Fri, 10 Jan 2003, Carsten Ziegeler wrote: > > > We had this problem, when not the proper version of xalan was in the > > classpath or precisly in the web-inf/lib directory. > > Due to the movement of the libr

RE: Reason of HTMLSerializer exception

2003-01-10 Thread Stephan Michels
On Fri, 10 Jan 2003, Carsten Ziegeler wrote: > We had this problem, when not the proper version of xalan was in the > classpath or precisly in the web-inf/lib directory. > Due to the movement of the libraries into the endorsed directory we > ended up having no xalan/xerces version in web-inf/li

RE: Reason of HTMLSerializer exception

2003-01-10 Thread Carsten Ziegeler
We had this problem, when not the proper version of xalan was in the classpath or precisly in the web-inf/lib directory. Due to the movement of the libraries into the endorsed directory we ended up having no xalan/xerces version in web-inf/lib and therefore the default version was used. HTH Carste