[ http://issues.apache.org/jira/browse/MYFACES-692?page=all ]
sean schofield closed MYFACES-692:
----------------------------------
Fix Version: Nightly
Resolution: Fixed
> AjaxPhaseListener does not work with forceId
> --------------------------------------------
>
> Key: MYFACES-692
> URL: http://issues.apache.org/jira/browse/MYFACES-692
> Project: MyFaces
> Type: Bug
> Components: Sandbox
> Versions: Nightly
> Reporter: sean schofield
> Fix For: Nightly
>
> I tried using inputSuggestAjax but ran into problems with forceId. The
> problem is that AjaxPhaseListener is relying on the clientId to be the
> default JSF assigned id that is used to identify the path of the component.
> It attempts to lookup the component using findComponentById which won't work
> with forceId.
> I suggest we consider changing the AjaxComponent interface from encodeAjax to
> processAjax. Then call every component in the tree giving each component
> that is intanceof AjaxComponent a chance to processAjax. Then the components
> themselves can check the submitted value against their clientId (simliar to
> decoding.) This approach will likely be slower but IMO forceId is a must
> have for my javascript (and there is more of it coming in the next spec.)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
