regards,
Martin
On 8/12/05, Dennis Byrne <[EMAIL PROTECTED]> wrote:
Sorry to be one of those who ask something they could just do
themselves, but does it just recursively crawl an object
graph?
All my business beans are hibernate proxies, and I would hate
for x:saveState to trigger a lazy loading of the entire
database.
---- Original message ----
>Date: Fri, 12 Aug 2005 08:57:07 +0200
>From: Martin Marinschek <[EMAIL PROTECTED]>
>Subject: Re: saveState mystery
>To: MyFaces Discussion <[email protected]>
>
> saveState serializes the property of the bean (or
> the bean itself) to - depending on your settings for
> state saving in the web.xml, CLIENT_SIDE or
> SERVER_SIDE - to the browser or the server
> session...
>
> regards,
>
> Martin
>
> On 8/12/05, Dennis Byrne < [EMAIL PROTECTED]> wrote:
>
> Thank you for the reply. I take it the @value
> typically
> points to a property of a managed bean?
>
> I am currently reconstructing an object graph for
> each
> request by hammering the DB. Worse, this is in
> the
> constructors of the backend beans, rather than
> bound methods,
> for some user actions in order to avoid NullPExs
> that occur
> when request values are applied to an null object
> model. I
> lose navigation options in the event of problems
> because
> contructors have no return values.
>
> It sounds as though saveState can serialize
> it? Just
> curious, where's the bean go? Serialized to the
> browser, or
> some place on the file system?
>
> ---- Original message ----
> >Date: Fri, 12 Aug 2005 07:55:20 +0200
> >From: Mads Henderson <[EMAIL PROTECTED]>
> >Subject: Re: saveState mystery
> >To: MyFaces Discussion <
> [email protected]>
> >
> >x:saveState solves many problems by letting you
> save the
> state of a
> >request scope bean between requests. That is, it
> feels like
> having a
> >session scope bean as long as you need it. But
> you don't
> need to worry
> >about cluttering the session with unused
> data, As soon as
> you leave
> >the pages containing the x.savestate, the object
> is removed.
> >
> >We are using x.savestate all over our website,
> and has
> reduced the
> >number of session scope beans to one. That is the
> object
> holding the
> >user identification.
> >
> >/madsph
> >
> >On 8/12/05, [EMAIL PROTECTED]
> < [EMAIL PROTECTED]> wrote:
> >>
> >> My shop is standardizing on a CRUD model; the
> arguments
> center around
> >> request vs. session scope. What does
> x:saveState do?
> >>
> >> The javadocs for this element are incredibly
> informative.
> >> http://myfaces.apache.org/tlddoc/tomahawk/
> >>
> >> Dennis Byrne
> >>
> Dennis Byrne
Dennis Byrne
