Hi Joe!
I did do that, and my code resumed working. That's what made me realize
that it was likely that it had something to do with Sitemesh rather than
other parts of the project.
What I eventually figured out was that the break happened when I renamed a
menu.jsp file included with <jsp:include> to menu.jspf. This file was
included within the Sitemesh decorator. After I changed it to .jspf, it
stopped working, throwing no exceptions, returning only a blank web page.
I renamed it back to .jsp and it started working again.
I think I would understand why this is if I were to understand the
processing order of .jsp includes and Sitemesh decorators better. (I bet
you know!) But for now, I've advised my team not to use .jspf file
extension on our new projects which use Sitemesh.
Thanks,
Caden
On Fri, Jun 15, 2012 at 4:00 PM, Joe Walnes <j
...@walnes.com> wrote:
> If SiteMesh runs into an error, it should throw an exception.
> As a starting point, I recommend removing the SiteMesh filter from web.xml
> and see if you can your web-app still behaves as expected (albeit,
> undecorated).
> cheers
> -Joe
> On Fri, Jun 15, 2012 at 2:15 PM, Caden <ca...@cadenhowell.com> wrote:
>> Hi,
>> I had Sitemesh 2 running in my development environment until yesterday it
>> spontaneously (as far as I could tell) stopped working. Is there a way I
>> can force it to display messages if I am using log4j in my project? Is
>> there some debugging information parameter I can enable in the <filter>
>> settings in web.xml? Does it log errors to a file somewhere? What's
>> frustrating is that I get a blank web page and no errors in my log. I
>> don't know what's going on.
>> Thanks,
>> Caden