[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-1088) Application Framework doesn't play well with valueChangeListeners and rendered attributes

Guy Veraghtert (JIRA) jira-events at lists.jboss.org
Thu Mar 29 05:55:57 EDT 2007

     [ http://jira.jboss.com/jira/browse/JBSEAM-1088?page=all ]

Guy Veraghtert closed JBSEAM-1088.

    Fix Version/s: 1.2.1.GA
       Resolution: Done

I think we can close this issue: on 27/03/2007 Gavin made a commit with message "apply page parameters as soon as possible, since it works better with Home.isManaged()".

> Application Framework doesn't play well with valueChangeListeners and rendered attributes
> -----------------------------------------------------------------------------------------
>                 Key: JBSEAM-1088
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-1088
>             Project: JBoss Seam
>          Issue Type: Bug
>          Components: Core, Documentation, Framework
>    Affects Versions: 1.2.1.GA
>         Environment: JSF RI 1.2_04
>            Reporter: Guy Veraghtert
>             Fix For: 1.2.1.GA
>         Attachments: SEAM-1088.zip
> When following Chapter 10 of the reference documentation (EntityHome + page parameters), strange/unwanted behavior is seen.
> 1) ValueChangeListeners are always invoked, even if the value didn't change (old value is always null, or the default value)
> 2) In some cases, fields are not update when they have a rendered attribute.
> In the attached example:
> - the entered lastname (only shown when the entity is already persisted) will never be persisted: the input component is not decoded because in this phase the "rendered value expression" evaluates to false (the EntityHome object has not yet an id (page parameter) injected, so it returns a new SeamTestClass).
> - the valueChangeListener is always invoked because in the Process Validations Phase the EntityHome object returns a new SeamTestClass instead of the entity we are editing.
> Or the documentation must be updated to clarify this issue (or to use the PageScope as suggested by Gavin (see forum)), or the implementation must be adapted so that the page parameters are injected earlier (maybe indicate in pages.xml when they must be injected?) or ...

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the seam-issues mailing list