Yeah, as it turns out, this was the culprit. Jetty 6.x had issues with the
conditionality where TC 6.x did not.
<s:if test="%{ #blog.content != 'NoPost' }">
<ul>
<li>
<a >
<s:action var="blog" name="blog-menu1"/>
<s:property value="#blog.content" escape="false"/>
</a>
</s:if>
<ul>
<c:forEach var="i" begin="0" end="3">
<c:if test="${blogArray[i] != 'NoPost'}">
<li>
<c:set var="murl"
value="/child/displayTileFullWidth-m1i${i+1}"/>
<a href="<s:url value="%{#attr.murl}"/>">
<c:out value="${blogArray[i]}"
escapeXml="false"/>
</a>
</li>
</c:if>
</c:forEach>
</ul>
</li>
</ul>
Peace,
Scott
On Fri, Mar 20, 2009 at 1:39 PM, ChadDavis <chadmichaelda...@gmail.com>wrote:
> On Thu, Mar 19, 2009 at 11:12 AM, Wes Wannemacher <w...@wantii.com> wrote:
> > In theory, an app should work on any app server, but from time to time
> > I've found out about incompatibilities the hard way. For instance,
>
> Similarly, I found incompatibility in JSP parsers in the past. My
> issue was moving from TC to Weblogic, several years back, but the
> issue was due to Tomcat having a less strict enforcement of syntax
> rules than weblogic. This is like what Wes reports. It could be some
> syntax in the JSP that TC let's slip, and Jetty doesn't.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
> For additional commands, e-mail: user-h...@struts.apache.org
>
>
