[jira] Resolved: (STR-2597) Unexpected Tiles recursion on JSP errors?

["Henri Yandell (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/struts/browse/STR-2597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Henri Yandell resolved STR-2597.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 1.3.9
         Assignee:     (was: Struts Developers)

STR-3021 is fixed, so hopefully that takes care of this one too.

> Unexpected Tiles recursion on JSP errors?
> -----------------------------------------
>
>                 Key: STR-2597
>                 URL: https://issues.apache.org/struts/browse/STR-2597
>             Project: Struts 1
>          Issue Type: Bug
>          Components: Tiles
>    Affects Versions: Nightly Build
>         Environment: Operating System: other
> Platform: Other
>            Reporter: Joe Germuska
>             Fix For: 1.3.9
>
>
> I'm developing an application which uses more layers of <tiles:insert> than I
> have often used in the past.  It seems that when an error occurs during JSP
> execution within an inserted tile, something causes the wrapping tiles to be
> executed more than once.
> Sometimes, this is just visually annoying, as it may make a navigation element
> appear more than once when an error occurs; more recently, it has been more
> deeply annoying, because the recursive execution was showing me an error which
> was actually masking the true problem.  It took me a long time to recognize this
> and turn to solving the root problem.
> One could probably test this just by writing some tile sets and using a
> scriptlet to throw an exception from a nested JSP.  If I have some time, i'll
> try to do that, but right now I need to catch up for all the time lost by that
> masked error.
> I ascribe this problem to Tiles because when I changed one tiles:insert into a
> jsp:include, I saw one less level of nesting.
> Also of potential import: at least once while I was digging around, I seemed to
> get this nesting behavior in the absence of an exception -- but at that point I
> was too frustrated to really be able to isolate the issue and the variables.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.