I'll take that into consideration but it doesn't solve the problem
of the forEach and out tags failing. I really need to be able to
to use these tags to select into an xml source for other reasons
besides building options for a select.
In ongoing research into this an x:parse fails with the same exception
on another page. Again if I change my struts action to directly
reference the jsp it works instead of a tile definition.
So I tried one step further and tried two different tiles definitions.
One that referenced the pages directly and one that uses a tiles:insert
The tiles:insert version fails the same way and the tiles definition that
directly references the jsp works fine.
I had to change the @ to ~~ so the email wouldn't thinks its an executable
*** this is layout.jsp
<%~~ page language="java" %>
<%~~ taglib uri="/WEB-INF/tld/struts-tiles.tld" prefix="tiles" %>
<tiles:insert attribute="body-content" ignore="true" />
<definition name=".main" path="/WEB-INF/layout/layout.jsp">
<put name="body-content" value="/WEB-INF/pages/body.jsp"/>
</definition>
*** this definition causes the jsp to fail
<definition name=".main.js.jobsearch" extends=".main">
<put name="title" value="Job Search" />
<put name="body-content" value="/WEB-INF/pages/JobSearch.jsp" />
</definition>
*** this definition works
<definition name=".main.js.jobsearch"
path="/WEB-INF/pages/JobSearch.jsp" >
</definition>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
