In some cases, component event requests are incorrectly interpretted as render 
requests (with a page activation context)
------------------------------------------------------------------------------------------------------------------------

                 Key: TAPESTRY-2220
                 URL: https://issues.apache.org/jira/browse/TAPESTRY-2220
             Project: Tapestry
          Issue Type: Bug
          Components: tapestry-core
    Affects Versions: 5.0.10
            Reporter: Howard M. Lewis Ship
            Assignee: Howard M. Lewis Ship
            Priority: Blocker


The PageRenderDispatcher runs first, and it sees a URL like 
/folder/name.componentid   (clearly, an action URL) as page "/folder/index" 
activation context "name.componentId".

-- 
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]

Reply via email to