You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Korhonen, Kalle" <kk...@cisco.com> on 2005/02/02 23:51:04 UTC
RE: [jira] Created: (MYFACES-98) Allow x:dataTable to storeitsdata model in the component tree
> -----Original Message-----
> From: Alessandro Polverini [mailto:alex@nibbles.it]
> Subject: RE: [jira] Created: (MYFACES-98) Allow x:dataTable
> to storeitsdata model in the component tree
> On Tue, 2005-02-01 at 14:30 -0800, Korhonen, Kalle wrote:
> > I don't think there's a bug in the implementation of
> preserveDataModel.
> > It's quite understandable that if you are using
> pageScroller together
> > with the dataTable, you have to take care of saving the
> data yourself.
> Hello Kalle, and thanks for your reply.
> I don't understand well why preserveDataModel should not work
> if used with pageScroller. PageScroller is just a "normal"
> component providing pagination, what would differ if I
> implement it in my program instead of using it?
> What I mean is: if the array is correctly restored for my
> application, why it should not work for pageScroller?
Oh, the reason is simple. Since the preserveDataModel saves only what
the dataTable displays, and pageScrollers divides the data into multiple
pages, preserveDataModel happily remembers only the results displayed on
the first page.
> Anyway, since they both are myfaces components, I expect them
> to correctly work together so a warning or something similar
> in the documentation would be welcome.
I 100% agree with you there. Even better, pageScroller could "take
over", force the preserveDataModel in the datatable to reset to false
and/or have its own preserveDataModel. Volunteering to implement that?
:)
Kalle
> > -----Original Message-----
> > > From: Alessandro Polverini [mailto:alex@nibbles.it]
> > > Sent: Tuesday, February 01, 2005 3:21 AM
> > > To: MyFaces Development
> > > Cc: Sean Schofield; martin@marinschek.com
> > > Subject: Re: [jira] Created: (MYFACES-98) Allow
> x:dataTable to store
> > > itsdata model in the component tree
> > >
> > > On Tue, 2005-02-01 at 09:25 +0100, Martin Marinschek wrote:
> > > > Exactly, use the preserveDataModel attribute and you
> are all set!
> > > >
> > > > Manfred had a very hard time implementing that one, as far as I
> > > > remember ;)
> > >
> > > Hello Martin,
> > > I tried to set preserveDataModel to true to avoid the x:saveState
> > > declaration, but this would not work (in my case, at least).
> > >
> > > I try to explain my situation to better understand the
> > > behaviour: I have a simple form with some search parameters, when
> > > the user submits it, the backing bean (request scope) is
> populated
> > > with results and I show and paginate through them using
> x:dataTable
> > > and x:dataScroller.
> > >
> > > The only way I found to make it work well is:
> > > - set preserveDataModel to false (or to not put the attribute
> > > completely)
> > > - use a x:saveState on #{bean.results}
> > >
> > > Whithout doning this, I can see only the first page of
> results and
> > > every other action (for example switch to page
> > > #2) the datas are lost and no more rows are displayed.
> > > The problem also occurs if I *both* use saveState and
> > > preserveDataModel, maybe because the partially conflicts in their
> > > operation?
> > >
> > > So, I deduce that preserveDataModel does not the very
> same thing of
> > > saveState, and maybe the idea of Sean is useful anyway?
> > >
> > > Or maybe preserveDataModel has a bug (or a limitation)
> and should be
> > > fixed?
> > >
> > > I would be interested to better understand this issue.
> > >
> > > Thanks,
> > > Alex
> > >
> > >
>
>
Re: ADF Faces EA13 released - announces MyFaces compatibility.
Posted by Matthias Wessendorf <ma...@matthias-wessendorf.de>.
Jonas,
that sounds nice!
I looked your blog and saw the howtos!
cool!
-Matthias
Jonas Jacobi wrote:
> Hi All,
>
> As I mentioned in a previous thread about ADF Faces and MyFaces, I'm now
> very pleased to announce the release of EA13. EA13 has been tested, and
> is compatible with MyFaces v.1.0.8. Oracle's OC4J 9.0.4 and Tomcat 5.0
> was used for our testing.
>
> http://www.oracle.com/technology/products/jdev/htdocs/partners/addins/exchange/jsf/index.html
>
>
> Thanks
> - Jonas
>
--
Matthias Weßendorf
Aechterhoek 18
DE-48282 Emsdetten
Germany
phone: +49-2572-9170275
cell phone: +49-179-1118979
email: matzew AT apache DOT org
url: http://www.wessendorf.net
callto://mwessendorf (Skype)
icq: 47016183
ADF Faces EA13 released - announces MyFaces compatibility.
Posted by Jonas Jacobi <jo...@oracle.com>.
Hi All,
As I mentioned in a previous thread about ADF Faces and MyFaces, I'm now
very pleased to announce the release of EA13. EA13 has been tested, and
is compatible with MyFaces v.1.0.8. Oracle's OC4J 9.0.4 and Tomcat 5.0
was used for our testing.
http://www.oracle.com/technology/products/jdev/htdocs/partners/addins/exchange/jsf/index.html
Thanks
- Jonas
ADF Faces EA13 released - announces MyFaces compatibility.
Posted by Jonas Jacobi <jo...@oracle.com>.
Hi All,
As I mentioned in a previous thread about ADF Faces and MyFaces, I'm now
very pleased to announce the release of EA13. EA13 has been tested, and
is compatible with MyFaces v.1.0.8. Oracle's OC4J 9.0.4 and Tomcat 5.0
was used for our testing.
http://www.oracle.com/technology/products/jdev/htdocs/partners/addins/exchange/jsf/index.html
Thanks
- Jonas
Re: [jira] Created: (MYFACES-98) Allow x:dataTable to storeitsdata model in the component tree
Posted by Sean Schofield <se...@gmail.com>.
Definitely get some of this discussion in JIRA. IMO its ok to have
the discussion through JIRA (instead of replying to email from JIRA).
This way the conversation is preserved along with the bug. Someday
when someone finds this JIRA bug they won't have to ask "What was this
person thinking?"
sean
RE: [jira] Created: (MYFACES-98) Allow x:dataTable to storeitsdata
model in the component tree
Posted by Alessandro Polverini <al...@nibbles.it>.
On Wed, 2005-02-02 at 14:51 -0800, Korhonen, Kalle wrote:
[...]
> > > It's quite understandable that if you are using
> > pageScroller together
> > > with the dataTable, you have to take care of saving the
> > data yourself.
> > Hello Kalle, and thanks for your reply.
> > I don't understand well why preserveDataModel should not work
> > if used with pageScroller. PageScroller is just a "normal"
> > component providing pagination, what would differ if I
> > implement it in my program instead of using it?
> > What I mean is: if the array is correctly restored for my
> > application, why it should not work for pageScroller?
>
> Oh, the reason is simple. Since the preserveDataModel saves only what
> the dataTable displays, and pageScrollers divides the data into multiple
> pages, preserveDataModel happily remembers only the results displayed on
> the first page.
Thanks for the explanation, now this is much clearer to me now :)
> > Anyway, since they both are myfaces components, I expect them
> > to correctly work together so a warning or something similar
> > in the documentation would be welcome.
>
> I 100% agree with you there. Even better, pageScroller could "take
> over", force the preserveDataModel in the datatable to reset to false
> and/or have its own preserveDataModel. Volunteering to implement that?
> :)
:)
I'm sorry I'm not skilled enough to add a similar feature, anyway I find
it could be useful a feature request on jira to not forget this great
suggestion. Can you enter it since you could certainly explain the thing
better than me? (otherwise tell me and I'll do it c&p your text
above ;) )
Thanks,
Alex