Re: Re: Trinidad table paging

2007-07-16 Thread Adam Winer
ns state and navigation with > this framework. I will seriously consider it for any serious JSF > application development requiring conversation scope. > > -Message d'origine- > De: news [mailto:[EMAIL PROTECTED] De la part de Laurie Harper > Envoyé: 13 juillet 2007 17:3

Re: Re: Trinidad table paging

2007-07-16 Thread Francisco Passos
scope. -Message d'origine- De: news [mailto:[EMAIL PROTECTED] De la part de Laurie Harper Envoyé: 13 juillet 2007 17:38 À: users@myfaces.apache.org Objet: Re: Trinidad table paging Francisco Passos wrote: > Great to know you've got it working. > > I'm now using t

RE: Re: Trinidad table paging

2007-07-16 Thread Laperle, Denis
yé : 13 juillet 2007 17:38 À : users@myfaces.apache.org Objet : Re: Trinidad table paging Francisco Passos wrote: > Great to know you've got it working. > > I'm now using the process scope feature of Trinidad and it's works fine but >> it means that I will have to clear

Re: Trinidad table paging

2007-07-13 Thread Laurie Harper
Francisco Passos wrote: Great to know you've got it working. I'm now using the process scope feature of Trinidad and it's works fine but it means that I will have to clear the process scope context manually at the appropriate time within the application to avoid high memory consumption on the

Re: Trinidad table paging

2007-07-13 Thread Francisco Passos
ROTECTED] *Envoyé :* 13 juillet 2007 05:00 *À :* MyFaces Discussion *Objet :* Re: Trinidad table paging As I have come to understand, this is expected. Although personally I believe it is not intuitive at all for any user. What happens is your bean is request scoped and as such its contents are

RE: Trinidad table paging

2007-07-13 Thread Laperle, Denis
navigation cases and see what else I need to save within process scope variables in a typical CRUD application. Thank you Denis De : Francisco Passos [mailto:[EMAIL PROTECTED] Envoyé : 13 juillet 2007 05:00 À : MyFaces Discussion Objet : Re: Trinidad ta

Re: Trinidad table paging

2007-07-13 Thread Francisco Passos
As I have come to understand, this is expected. Although personally I believe it is not intuitive at all for any user. What happens is your bean is request scoped and as such its contents are lost when you make the second request. What you need is either request-scoped state saving (for instance