Details
Bug
Major
Description
When components are dynamically added, the id modification performed by autoid can get out of sync:
In Mojarra StateManagementStrategyImpl:
// handle dynamic adds/removes
List<String> removeList = stateContext.getDynamicRemoves();
if (null != removeList && !removeList.isEmpty()) {
stateMap.put(CLIENTIDS_TO_REMOVE_NAME, removeList);
}
Map<String, ComponentStruct> addList = stateContext.getDynamicAdds();
if (null != addList && !addList.isEmpty()) {
List<Object> savedAddList = new ArrayList<Object>(addList.size());
for (ComponentStruct s : addList.values()) {
savedAddList.add(s.saveState(context));
}
stateMap.put(CLIENTIDS_TO_ADD_NAME, savedAddList.toArray());
}
"dynamic adds" are populated with the original IDs set prior to autoid modification. When autoid modifies these IDs, they do not match the value expected by state saving.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
The strategy was to also listen for PreRenderViewEvent and to set a flag on the FacesContext. If the flag is set, subsequently added components will not have their IDs modified. This means that dynamically added components are not affected by autoid. The flag does not need to be cleared, as even if a postback occurs, the render process will only take place once.
Show
Ted Goddard
added a comment - The strategy was to also listen for PreRenderViewEvent and to set a flag on the FacesContext. If the flag is set, subsequently added components will not have their IDs modified. This means that dynamically added components are not affected by autoid. The flag does not need to be cleared, as even if a postback occurs, the render process will only take place once.
AbstractMenu.buildMenuFromModel() :
for(UIComponent kid : model.getSubmenus())
getChildren().add(kid);
called during encodeEnd for a variety of menu Renderers.