You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Leonardo Uribe (JIRA)" <de...@myfaces.apache.org> on 2008/03/01 05:47:51 UTC
[jira] Created: (MYFACES-1828) code that allow perform custom tasks
before and after set binding in 1.2 does not work
code that allow perform custom tasks before and after set binding in 1.2 does not work
--------------------------------------------------------------------------------------
Key: MYFACES-1828
URL: https://issues.apache.org/jira/browse/MYFACES-1828
Project: MyFaces Core
Issue Type: Bug
Affects Versions: 1.2.2, 1.2.0
Reporter: Leonardo Uribe
Assignee: Leonardo Uribe
Fix For: 1.2.3-SNAPSHOT
In myfaces 1.1, it was possible to have a method on the component like this
public void handleBindings()
{
makeAliases(getFacesContext());
RestoreStateUtils.recursivelyHandleComponentReferencesAndSetValid(getFacesContext(), this, true);
removeAliases(getFacesContext());
}
This is called from RestoreView state to handle the bindings properly. In myfaces 1.2, architectural changes (creation on RestoreViewSupport interface) replaced the original code with this:
public void processComponentBinding(FacesContext facesContext, UIComponent component)
{
ValueExpression binding = component.getValueExpression("binding");
if (binding != null)
{
binding.setValue(facesContext.getELContext(), component);
}
for (Iterator<UIComponent> iter = component.getFacetsAndChildren(); iter.hasNext();)
{
processComponentBinding(facesContext, iter.next());
}
}
Some changes are necessary on RestoreStateUtils.recursivelyHandleComponentReferencesAndSetValid (not set UIInput components valid = true) to make this work as 1.1 with the advantage of aliasBean component can work like 1.1.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.