If you're using client-side state saving, it's not using a session
object. It's using a hidden field.
Note also that if you're using server-side state saving and JSF 1.1,
then you can't have multiple pages open at the same time for the same
session. It's not supported. It does work with client-side state
saving, though.
On 8/31/07, Costa Basil <[EMAIL PROTECTED]> wrote:
> Thank you. I need to pass some objects from a page to a dialog opened from
> that page and I do not want to use session objects.
>
> Mike Kienenberger <[EMAIL PROTECTED]> wrote:
> Seems like a strange thing to do, but I guess you'd do it just like
> t:saveState.
>
> You'd point your h:hiddenText (is that the right name?) value to
> #{bean.objectState} and you'd have getObjectState serialize the object
> into a string, and setObjectState unserialize the object.
>
> On 8/31/07, Costa Basil wrote:
> > How do I serialize an object in a hidden field (as opposed to using
> > saveState and having its state meshed somewhere else along with the other
> > components)?
> >
> > Thanks
> >
> >
> > ________________________________
> > Be smarter than spam. See how smart SpamGuard is at giving junk email the
> > boot with the All-new Yahoo! Mail
> >
> >
>
>
>
> ________________________________
> Ask a question on any topic and get answers from real people. Go to Yahoo!
> Answers.
>
>
