myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Freedman (JIRA)" <...@myfaces.apache.org>
Subject [jira] Created: (PORTLETBRIDGE-178) Portlet Bridge 3.0.0 -- Support Views using Ajax that reference component ids (in the execute or render id list)
Date Thu, 03 Feb 2011 21:38:28 GMT
Portlet Bridge 3.0.0 -- Support Views using Ajax that reference component ids (in the execute
or render id list)
----------------------------------------------------------------------------------------------------------------

                 Key: PORTLETBRIDGE-178
                 URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-178
             Project: MyFaces Portlet Bridge
          Issue Type: Bug
            Reporter: Michael Freedman
            Assignee: Michael Freedman


The Faces 2.0 ajax javascript signature takes two parameters that allow you to identify the
targets of the action and the render.  Many samples, (and hence commonly) set these ids statically.
 This breaks when run in a portlet/bridge environment because the bridge wraps the entire
tree with its own UIViewRoot which adds a NamingContainer to ensure are ids are unique in
an overall portal page.  I.e. its NC prefix is prepended to the component id.  

So the problem is the request sends ids x, y, z while the tree contains nc.x, nc,y, nc.z.
 hence the ids aren't found and nothing is executed/rendered.

Fix is to write our own PartialViewContext which overrides getRenderIds() and getExecuteIds()
and take all the ids that don't resolve and retry them with the nc id prepended.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message