myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Marinschek (JIRA)" <>
Subject [jira] Closed: (MYFACES-687) aliasBean which includes elements with valueBinding attribute crashes during restoreView
Date Mon, 31 Oct 2005 02:24:57 GMT
     [ ]
Martin Marinschek closed MYFACES-687:

    Fix Version: Nightly
     Resolution: Fixed
      Assign To: Martin Marinschek

see MYFACES-686. Thanks to Stefan Betermieux

> aliasBean which includes elements with valueBinding attribute crashes during restoreView
> ----------------------------------------------------------------------------------------
>          Key: MYFACES-687
>          URL:
>      Project: MyFaces
>         Type: Bug
>   Components: Tomahawk
>     Versions: Nightly
>     Reporter: Stefan Betermieux
>     Assignee: Martin Marinschek
>      Fix For: Nightly

> Hi,
> after a long debug session I am pretty sure that there is a bug regarding aliasBeans
during restoreView phase.
> consider the following scenario:
> An aliasBean which contains elements, one of them has the binding="..." attribute set,
which uses a method in  the holder bean.
> During LifecycleImpl.restoreView(), the holder bean is initialized only sometime during
the viewHandler.restoreView() call, no problem so far.
> During the recursivelyHandleComponentReferencesAndSetValid() the method bindig.isReadOnly()
is called. The holder bean is null, it can't find the property, it returns false because the
general exception is catched. After this recursivelyHandleComponentReferencesAndSetValid()
thinks it can write the reference and tries to call binding.setValue(). This fails miserably
and an uncaught exception is thrown (javax.faces.el.PropertyNotFoundException: Base is null:
> I don't really know how to fix this, but since my binding is read only anyway, I would
be happy if binding.isReadOnly() returns the more pessimistic "true" instead of letting binding.setValue()
crash. See JIRA MYFACES-686 for my first take on this issue.
> Stefan

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