myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Marinschek (JIRA)" <>
Subject [jira] Commented: (MYFACES-692) AjaxPhaseListener does not work with forceId
Date Tue, 18 Oct 2005 10:13:45 GMT
    [ ] 

Martin Marinschek commented on MYFACES-692:

You are right - there are now some issues coming up with the intended AJAX-architecture.

We will need something more than we have right now, and maybe you want to start a developer



> AjaxPhaseListener does not work with forceId
> --------------------------------------------
>          Key: MYFACES-692
>          URL:
>      Project: MyFaces
>         Type: Bug
>   Components: Sandbox
>     Versions: Nightly
>     Reporter: sean schofield
>     Priority: Blocker

> 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:
For more information on JIRA, see:

View raw message