Hmmm... while this approach displays the page OK, I get the error below
in my JBoss console when executing the action. Is this something I need
to prevent with some sort of page directive?
2008-03-06 13:14:11,470 ERROR
[org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/DataCa
ll].[jsp]] Servlet.service() for servlet jsp threw exception
java.io.IOException: Stream closed
at
org.apache.jasper.runtime.JspWriterImpl.ensureOpen(JspWriterImpl.java:20
4)
at
org.apache.jasper.runtime.JspWriterImpl.flushBuffer(JspWriterImpl.java:1
15)
at
org.apache.jasper.runtime.PageContextImpl.release(PageContextImpl.java:1
86)
at
org.apache.jasper.runtime.JspFactoryImpl.internalReleasePageContext(JspF
actoryImpl.java:117)
at
org.apache.jasper.runtime.JspFactoryImpl.releasePageContext(JspFactoryIm
pl.java:76)
at
org.apache.jsp.fragments.root_jsp._jspService(root_jsp.java:106)
at
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.ja
va:373)
at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:336)
at
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica
tionFilterChain.java:290)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt
erChain.java:206)
at
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatc
her.java:654)
at
org.apache.catalina.core.ApplicationDispatcher.processRequest(Applicatio
nDispatcher.java:445)
at
org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDisp
atcher.java:379)
at
org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispat
cher.java:292)
at
org.apache.tiles.servlet.context.ServletTilesRequestContext.forward(Serv
letTilesRequestContext.java:198)
at
org.apache.tiles.servlet.context.ServletTilesRequestContext.dispatch(Ser
vletTilesRequestContext.java:185)
at
org.apache.tiles.context.TilesRequestContextWrapper.dispatch(TilesReques
tContextWrapper.java:72)
at
org.apache.struts2.tiles.StrutsTilesRequestContext.dispatch(StrutsTilesR
equestContext.java:86)
at
org.apache.tiles.impl.BasicTilesContainer.render(BasicTilesContainer.jav
a:419)
at
org.apache.tiles.impl.BasicTilesContainer.render(BasicTilesContainer.jav
a:370)
at
org.apache.struts2.views.tiles.TilesResult.doExecute(TilesResult.java:10
4)
at
org.apache.struts2.dispatcher.StrutsResultSupport.execute(StrutsResultSu
pport.java:178)
at
com.opensymphony.xwork2.DefaultActionInvocation.executeResult(DefaultAct
ionInvocation.java:348)
-----Original Message-----
From: Martin Gainty [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 06, 2008 9:51 AM
To: Griffith, Michael *
Cc: Struts Users Mailing List
Subject: Re: How can I combine a result (tiles + xslt)?
Michael-
remembering our academic coursework teaches Not(Not condition) evaluates
positive
be sure to set ignoreContextParams="false" as in <s:action tag
ignoreContextParams="false" ...>
I would encourage you to read Dave's article on using ResultTypes at
http://struts.apache.org/2.x/docs/result-types.html
MG
----- Original Message -----
From: "Griffith, Michael *" <[EMAIL PROTECTED]>
To: "Struts Users Mailing List" <user@struts.apache.org>
Sent: Thursday, March 06, 2008 10:16 AM
Subject: RE: How can I combine a result (tiles + xslt)?
Hi Wes,
Thanks for the reply. The s:action tag seems to work. I have a tiles
action that is the actual URL that the user would navigate to, and in
the JSP fragment that is the body tile, I am using the s:action to
invoke the XSLT action and return the HTML fragment for the body.
Thanks so much for pointing this out, I was not aware of this tag.
Cheers!
MG
-----Original Message-----
From: Wes Wannemacher [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 05, 2008 4:49 PM
To: Struts Users Mailing List
Subject: Re: How can I combine a result (tiles + xslt)?
On Wed, 2008-03-05 at 17:18 -0500, Griffith, Michael * wrote:
[snip]
>
>
> Is this a good application for writing my own interceptor for?
You would want to write your own "Result Type" for this. Writing your
own results is not as well documented as writing your own interceptors,
but since you are combining the functionality of two built-in result
types, it may be "pretty simple."
Another possible choice would be to use the s:action tag with
executeResult set to true...
http://struts.apache.org/2.x/docs/action.html
Then, have one action that uses a tiles result, but in that result, have
the s:action call the action which will render the xslt result.
-Wes
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
