So I was able to use typical page troubleshooting - I commented out the
SiteMesh filter to see what was happening with my content, and it worked
fine. So then I re-enabled SiteMesh and started commenting out sections of
the decorator JSP.
It turned out that the problematic part was a dynamic JSP include at the end
of the decorator that pulls in a footer. I guessed that Acegi was trying to
secure that JSP since the securityFilter was set up as
<filter-mapping>
<filter-name>securityFilter</filter-name>
<url-pattern>/*</url-pattern>
</filter-mapping>
I modified the filter-mapping to look like
<filter-mapping>
<filter-name>securityFilter</filter-name>
<url-pattern>/j_security_check</url-pattern>
</filter-mapping>
<filter-mapping>
<filter-name>securityFilter</filter-name>
<url-pattern>/WEB-INF/pages/*.jsp</url-pattern>
</filter-mapping>
and it works now. Oh, also I moved the declaration of the SiteMesh filter
to the end of the declared filters in web.xml. That eliminated an extra
call back to sitemesh's PageFilter.doFilter() callback. I am not sure why
but even at the very end of the filter chain, the SM PageFilter gets invoked
5 times. No worries because an attribute is set and the redundant calls are
aborted, but still, strange.
--
View this message in context:
http://www.nabble.com/Page-not-loading-tp20260419s2369p20374135.html
Sent from the AppFuse - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
