myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Heinen (JIRA)" <>
Subject [jira] Commented: (TOMAHAWK-764) ValueBinding lost for first attribute
Date Wed, 01 Nov 2006 18:51:19 GMT
    [ ] 
Michael Heinen commented on TOMAHAWK-764:

I am using a4j and it's working like a charm.

There are some situations where I think I have to bind the first attribute because it has
to be updated in the BB. 
I have some ajaxlinks which apply a filter on the datatable or remove a filter. This means
that the number of elements in the table is dynamic.  When I add or remove a filter then I
have to set the first attribute back to page 0. The problem is now that the datascroller erased
this valueBinding before.
(Pls see my first link where I described such a szenario in more detail).

I don't see any other alternatives as a valueBinding. Pls correct me if I'm wrong.


> ValueBinding lost for first attribute
> -------------------------------------
>                 Key: TOMAHAWK-764
>                 URL:
>             Project: MyFaces Tomahawk
>          Issue Type: Bug
>          Components: Extended Datatable
>    Affects Versions: 1.1.4-SNAPSHOT, 1.1.3
>         Environment: myFaces core1.1.4
> tomahawk 1.1.4 Snapshot
>            Reporter: Michael Heinen
> There is a major bug using the t:datatable in conjunction with the t:datascroller and
a valueBinding for the first attribute.
> The HtmlDataScroller erases this value binding due to the fact, that it calls setFirst
with an int in the broadcast method.
> If the page is then reloaded via ajax, then first contains a pagenumber instead of the
> Patch for setFirst:
>     public void setFirst(int first)
>     {
>       ValueBinding vb = getValueBinding("first");
>       if (vb != null)
>       {
>         //do nothing and keep the valueBinding
>         return;
>       }
>       else
>         if (_preservedDataModel != null)
>         {
>             //Also change the currently restored DataModel attribute
>             _preservedDataModel.setFirst(first);
>         }
>         super.setFirst(first);
>     }   
> see this threads:
> Michael

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