[
http://www.stripesframework.org/jira/browse/STS-788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12135#comment-12135
]
Nicholas Stuart commented on STS-788:
-------------------------------------
Ben, this is in reply to your comment on STS-791. I'm looking at the latest SVN
code for 1.5.5, r1369
It appears this second scenario is loosing the context or the context is not
correct when rendering the nested component. Debugging through, everything
looks fine running through LayoutComponentRenderer, it goes in and renders the
regular components fine, and when it gets to the nested component it enters the
loop just fine at line 119 and acts like the other ones Howver, something goes
wrong when it goes to include the pageContext at 133:
pageContext.include(context.getRenderPage(), false)...
When the other two are rendering I hit the if (isCurrentComponent()) line 107
twice, showing each component in the context and it evals the body when the
current component is set correctly. When the nested component goes to get
rendered though the current component is never set to it . Instead I just the
two 'regular' components from the first layout, and thats it. It's like the
second-render tags body is never being evaluated correctly from the page. If
the secondary layout has default content in the component, that will in fact
get displayed. But if that content is in the regular page, it never gets
evaluated
It's all fairly confusing, and guessing it's that way to get the components to
render when available and flushing when they can, but it does have the
unfortunate side affect of being hard to follow....
> Layout issues after upgrade from 1.5.3
> --------------------------------------
>
> Key: STS-788
> URL: http://www.stripesframework.org/jira/browse/STS-788
> Project: Stripes
> Issue Type: Bug
> Components: Tag Library
> Affects Versions: Release 1.5.4
> Environment: jetty-6.1.15, Java(TM) SE Runtime Environment (build
> 1.6.0_22-b04-307-10M3261)
> Reporter: David Dundua
> Assignee: Ben Gunter
> Fix For: Release 1.5.5
>
> Attachments: stripes-bug.zip
>
>
> Guys, I have a couple of layout scenarios which stopped working after
> upgrading to 1.5.4. I have created a couple of test cases demonstrating
> these issues. I am attaching maven2 project.
> 1. mvn jetty:run
> 2. http://localhost:8080/stripes-bug
> 3. take a look at the output of each test under 1.5.4
> 4. change the stripes dependency to 1.5.3
> 5. mvn clean jetty:run
> 6. observe the difference in the output
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment, and,
should the need arise, upgrade to a full multi-node Oracle RAC database
without downtime or disruption
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Stripes-development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-development
