Re: x:dataScroller blanked on page change

[Mark <mf...@knology.net>]

Sean Schofield wrote:

>Request scope works fine.  Try the simple examples that ship with the
>source (or download them from the nightlies.)  Modify the scope of the
>managed bean used by pagedSortTable.jsp and you can see that it works
>fine.
>
>sean
>
>On 31 May 2005 12:48:52 -0000, mfaine <mf...@knology.net> wrote:
>  
>
>>It seems you are right.  I am not reloading the list on each request.  The
>>bean is session scoped.  I have set it to request scope to test and the
>>dataScroller functions correctly.  I guess this means that a x:dataScroller
>>will not work with a session scoped bean?  Someone please correct me if I'm
>>wrong.  I have checkboxes on the page that onchange do submit() which also
>>reloads the list and causes problems.  The effect is if you check a box the
>>page reloads and the box is unchecked.  Not what was intended. I need for
>>the x:dataScroller to not need the list reloaded so that I may keep the bean
>>in session scope, or failing that I need to be able to reload the list
>>without setting the bean to request scope.  Any ideas or suggestions would
>>be appreciated.
>>
>>Thanks,
>>-Mark
>>    
>>


I'm aware that request scope works but does session?  I would like for my bean to remain session scoped if at all possible.

-Mark

Re: x:dataScroller blanked on page change

[Sean Schofield <se...@gmail.com>]

Session scope works too.  That is the scope of the bean in the
example.  Do you have input components in your datatable?  If so, see
this bug (http://issues.apache.org/jira/browse/MYFACES-228) for an
explanation (solution is in the works but will be tricky.)

sean

On 5/31/05, Mark <mf...@knology.net> wrote:
> Sean Schofield wrote:
> 
> >Request scope works fine.  Try the simple examples that ship with the
> >source (or download them from the nightlies.)  Modify the scope of the
> >managed bean used by pagedSortTable.jsp and you can see that it works
> >fine.
> >
> >sean
> >
> >On 31 May 2005 12:48:52 -0000, mfaine <mf...@knology.net> wrote:
> >
> >
> >>It seems you are right.  I am not reloading the list on each request.  The
> >>bean is session scoped.  I have set it to request scope to test and the
> >>dataScroller functions correctly.  I guess this means that a x:dataScroller
> >>will not work with a session scoped bean?  Someone please correct me if I'm
> >>wrong.  I have checkboxes on the page that onchange do submit() which also
> >>reloads the list and causes problems.  The effect is if you check a box the
> >>page reloads and the box is unchecked.  Not what was intended. I need for
> >>the x:dataScroller to not need the list reloaded so that I may keep the bean
> >>in session scope, or failing that I need to be able to reload the list
> >>without setting the bean to request scope.  Any ideas or suggestions would
> >>be appreciated.
> >>
> >>Thanks,
> >>-Mark
> >>
> >>
> 
> 
> I'm aware that request scope works but does session?  I would like for my bean to remain session scoped if at all possible.
> 
> -Mark
> 
>