[
http://www.stripesframework.org/jira/browse/STS-405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Fennell resolved STS-405.
-----------------------------
Resolution: Fixed
Fix Version/s: Release 1.5
The reason this check exists is because some containers, notably Tomcat, will
silently ignore includes of non-existent URLs. This can be very confusing
because there is no outward sign of what went wrong.
I've reworked things to instead include a flag on the LayoutContext that is set
when the layout is actually rendered (inside the include()). The LayoutRender
tag then checks this flag and throws an exception if it didn't get set. The
end result is that the desired behaviour (obvious errors) is the same as
before, but without the requirement that Stripes be able to find a
file/resource matching the layout.
> LayoutRenderTag.java refuses to work with JSP-less deployment
> -------------------------------------------------------------
>
> Key: STS-405
> URL: http://www.stripesframework.org/jira/browse/STS-405
> Project: Stripes
> Issue Type: Bug
> Components: Tag Library
> Affects Versions: Release 1.4.3
> Environment: JBoss 4.2.0-GA
> Reporter: Martin Buechler
> Fix For: Release 1.5
>
>
> While doing live deployment of our stripes-powered webapp to JBoss we
> encounter a
> showstopper caused by stripes' LayoutRenderTag. Since we deploy an exploded
> ear, containing only JSP-generated class files, no JSP's and do not want
> precomiling as you maybe
> want in an integration or development environment, threre is IMHO no need to
> rely on the fact that there is somewhere in the file sytem the source JSP
> lying
> around.
> In line 109 of
> http://stripes.svn.sourceforge.net/viewvc/stripes/tags/1.4.3/stripes/src/net/sourceforge/
> stripes/tag/layout/LayoutRenderTag.java
> URL target =
> request.getSession().getServletContext().getResource(this.name);
> stripes is checking for the physical presence of the JSP. Maybe one should
> also
> check for an existing servlet mapping, as it is available when pre-compiled
> and
> pre-loaded JSP servlets are engaged, before throwing that exception. For now I
> patched stripes, but would realy see that included in a future release.
> Besides I consider stripes as a real alternative to struts and fun to use.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://www.stripesframework.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Stripes-development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-development
