[
https://issues.apache.org/jira/browse/TAPESTRY-2044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Howard M. Lewis Ship reassigned TAPESTRY-2044:
----------------------------------------------
Assignee: Howard M. Lewis Ship
> Component action requests are not capable of handling the case where the
> active page and the page containing the component are different
> ----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TAPESTRY-2044
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2044
> Project: Tapestry
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.0.7
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Priority: Blocker
>
> This can happen when page A renders a block from page B that contains
> component C. In this case, page A's logical name and activation context
> should go into the URL, as well as page B's logical name, and page C's nested
> id and event context. The current implementations (of LinkFactory,
> Dispatcher, etc.) assume that page A is always the same as page B.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
