Hello,

I'm sorry for the forward, but Scott from Sitemesh thought that a
problem I was experiencing was a Tomcat bug.

Below is a stacktrace I'm experiencing when running the sitemesh example
webapp in Tomcat 5.0.16 (SuSE 9, JDK 1.4.2). Scott thinks it's a Tomcat
5 bug.

Would the stacktrace appear to be a problem with the sitemesh example
webapp or with Tomcat?

Thanks very much for your help,
Seth



-------- Original Message --------
Subject: Re: [Opensymphony-sitemesh] Problems with SM 2.0.1 Example and
Tomcat 5.0.16
Date: Mon, 15 Dec 2003 15:38:59 +1100
From: Scott Farquhar <scott@(protected)>
To: Seth Ladd <seth@(protected)>
CC: opensymphony-sitemesh@(protected)
References: <3FDA170A.70806@(protected)>

Seth,

I believe that Sitemesh runs fine under Tomcat 4, but it hasn't been
tested yet on Tomcat 5.

From the stack trace, it looks like a Tomcat 5 bug - you should always
be able to get a writer from a JSP?

Can you try the test suite and see if it works for you?

Cheers,
Scott

Seth Ladd wrote:

> Hello,
>
> I am just experimenting with SiteMesh, and ran into some problems. I
> have deployed the sitemesh-example.war from the 2.0.1 release to Tomcat
> 5.0.16.
>
> The first problem I have is that the web.xml contains some invalid configs.
>
> The <url-pattern>*</url-pattern> should be
> <url-pattern>/*</url-pattern>. Once I changed this, the war was able to
> deploy.
>
> Then, when I try to access the example webapp, I receive this error:
>
> java.lang.IllegalStateException: getOutputStream() has already been
> called for this response
>   org.apache.coyote.tomcat5.CoyoteResponse.getWriter (CoyoteResponse.java:611)
>
>   org.apache.coyote.tomcat5.CoyoteResponseFacade.getWriter (CoyoteResponseFacade.java:190)
>
>   javax.servlet.ServletResponseWrapper.getWriter (ServletResponseWrapper.java:156)
>
>   org.apache.jasper.runtime.JspWriterImpl.initOut (JspWriterImpl.java:167)
>   org.apache.jasper.runtime.JspWriterImpl.flushBuffer (JspWriterImpl.java:160)
>
>   org.apache.jasper.runtime.JspWriterImpl.flush (JspWriterImpl.java:214)
>   org.apache.jasper.runtime.JspRuntimeLibrary.include (JspRuntimeLibrary.java:990)
>
>   org.apache.jasper.runtime.PageContextImpl.include (PageContextImpl.java:626)
>
>   com.opensymphony.module.sitemesh.taglib.page.ApplyDecoratorTag.doEndTag (ApplyDecoratorTag.java:254)
>
>   org.apache.jsp.decorators.main_jsp._jspx_meth_page_applyDecorator_0(main_jsp.java:171)
>
>   org.apache.jsp.decorators.main_jsp._jspService(main_jsp.java:80)
>   org.apache.jasper.runtime.HttpJspBase.service (HttpJspBase.java:133)
>   javax.servlet.http.HttpServlet.service (HttpServlet.java:856)
>   org.apache.jasper.servlet.JspServletWrapper.service (JspServletWrapper.java:311)
>
>   org.apache.jasper.servlet.JspServlet.serviceJspFile (JspServlet.java:301)
>
>   org.apache.jasper.servlet.JspServlet.service (JspServlet.java:248)
>   javax.servlet.http.HttpServlet.service (HttpServlet.java:856)
>   com.opensymphony.module.sitemesh.filter.PageFilter.applyDecorator (PageFilter.java:169)
>
>   com.opensymphony.module.sitemesh.filter.PageFilter.doFilter (PageFilter.java:68)
>
>
>
> I'm not sure how to fix this one. Any ideas or tips?
>
> Thanks very much!
> Seth
>




---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@(protected)
For additional commands, e-mail: tomcat-user-help@(protected)