incubator-adffaces-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Lowe" <>
Subject Re: Saving model state between requests
Date Thu, 14 Dec 2006 11:00:56 GMT
I don't know of any ADF/Trinidad alternative to preserveDataModel, but then
again I am quite new to this component set.

I've been using Trinidad along with Facelets and JBoss Seam. There have been
some discussions around Tomahawk and in particular the "preserveDataModel"
flag not playing well with either of these technologies:

Long story short - best not to use it!

A general JSF solution to this would be to store your data model (or
whatever collection that drives the datamodel) in a session bean which will
serve as a data cache between requests. In the restore view phase - use the
cached version; in prerender phase refresh the cached list.  It ain't pretty
- but it worked for me.

BTW Seam offers some neat solutions to this problem ranging from a version
of the above JSF method but needing only a couple of annotations through to
the caching of already rendered page fragments.



On 13/12/06, Meyer, Stefan <> wrote:
> I have a pretty common problem with tables. I put a button in a table
> column. A "setActionListener" makes sure that the called action can
> access the id of the entity the column represents and the action can
> operate on that entity. The CollectionModel needs to be present before
> "model update" so that the actionListener can retrieve the data from it.
> In tomahawk there is the attribute "preserveDataModel" in order to
> persist the datamodel from request to request. Another option is the use
> of "saveState" component. I understand that loading the data freshly has
> advantages but in my case  it might be pretty slow (Lucene query). Is
> there a way to do preserve the datamodel in trinidad?

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message