Re: MyFaces Tomahawk

[Mike Kienenberger <mk...@gmail.com>]

Rick,

Sorry.  I can't help you.   I've never used the JSF RI, nor do I use
server-side state saving.

You could either implement the special phase listener described in 
TOMAHAWK-134 or you could try asking on the JSF RI list why
saveState/restoreState aren't called for server-side state saving.

I'm cc'ing your message to the "MyFaces User mailing list"
<us...@myfaces.apache.org> as you're far more likely to get help there
than emailing me directly.

On 3/21/06, Rick Nendza <rn...@gmail.com> wrote:
> Hi Mike,
>
> I'm really sorry to bother you. Your probably not the right person but I've
> noticed activity on this JIRA but yet no patch to grab.
> I promise to start contributing in the future! Any help would be appreciated
> it as I'm at a desperate standstill!
>
> I'm a independent consultant for IBM (previous employed by IBM) helping them
> with development of a web requisition system.
>
> I'm really desperate for some sort of solution / patch for JIRA 134 (
> https://issues.apache.org/jira/browse/TOMAHAWK-134)
>
> The client insists on using the Sun 1.1 RI with IBM extensions and allows
> Tomahawk extensions (using RAD 6.0.1 for development)
> They insist on using STATE_SAVING_METHOD  set to the server.
>
> I need to maintain a backing bean that contains a complex object graph (all
> objects serializable) for which its data was not easy to get (many many db
> queries).
> I simply need to maintain this duing the reload of the page or trigger of an
> post that redisplays the page for that matter.
>
> I've looked at t:saveState and it apears that the SUN RI refuses to call
> saveState() / restoreState() on the UIComponent when using a server
> STATE_SAVING_METHOD.
> I've looked at ADF and client deems it too drastic to incorporate at this
> time.
> I've looked at flowState done by the boys at Berkley but wasn't unable to
> get that to work either because I'm simply not implementing it right or
> perhaps they were reliant on Client STATE_SAVING_METHOD with the SUN at the
> time it was development.. not sure.
>
> Thanks Man!
>
>
>
>
>
>
>

Re: MyFaces Tomahawk

[Adam Winer <aw...@gmail.com>]

In server-side state saving?  The 1.1 RI doesn't support simultaneous
requests from the same user from two windows;  it only works for client-
side state saving.  The JSF 1.1 algorithm for server-side state saving -
just storing the UIViewRoot - necessarily implies that saveState() will
not be called, and that's not a bug.

As of JSF 1.2, both server-side and client-side state saving will
end up invoking saveState(), because the algorithm for server-side
state saving is entirely different in 1.2.  I forget how much of this
is specified vs. implementation-specific.

-- Adam


On 3/23/06, Martin Marinschek <ma...@gmail.com> wrote:
> I really wonder how the RI goes about providing a different state tree
> for a user if the user has two requests running from the same browser.
>
> regards,
>
> Martin
>
> On 3/23/06, Werner Punz <we...@gmx.at> wrote:
> > Actually this seems either like a bug in the RI to me, since savestate
> > does nothing fancy which should not work in the RI. It basically just
> > does what every component does in the save and restore phase. Or a bug
> > by the user.
> >
> > Maybe some of the classes in the original tree are not serializable,
> > which could cause a problem, due to the fact that the beans themselves
> > are serialized by saveState.
> >
> >
> >
> > Mike Kienenberger schrieb:
> > > Rick,
> > >
> > > Sorry.  I can't help you.   I've never used the JSF RI, nor do I use
> > > server-side state saving.
> > >
> > > You could either implement the special phase listener described in
> > > TOMAHAWK-134 or you could try asking on the JSF RI list why
> > > saveState/restoreState aren't called for server-side state saving.
> > >
> > > I'm cc'ing your message to the "MyFaces User mailing list"
> > > <us...@myfaces.apache.org> as you're far more likely to get help there
> > > than emailing me directly.
> > >
> >
> >
>
>
> --
>
> http://www.irian.at
>
> Your JSF powerhouse -
> JSF Consulting, Development and
> Courses in English and German
>
> Professional Support for Apache MyFaces
>

Re: MyFaces Tomahawk

[Martin Marinschek <ma...@gmail.com>]

I really wonder how the RI goes about providing a different state tree
for a user if the user has two requests running from the same browser.

regards,

Martin

On 3/23/06, Werner Punz <we...@gmx.at> wrote:
> Actually this seems either like a bug in the RI to me, since savestate
> does nothing fancy which should not work in the RI. It basically just
> does what every component does in the save and restore phase. Or a bug
> by the user.
>
> Maybe some of the classes in the original tree are not serializable,
> which could cause a problem, due to the fact that the beans themselves
> are serialized by saveState.
>
>
>
> Mike Kienenberger schrieb:
> > Rick,
> >
> > Sorry.  I can't help you.   I've never used the JSF RI, nor do I use
> > server-side state saving.
> >
> > You could either implement the special phase listener described in
> > TOMAHAWK-134 or you could try asking on the JSF RI list why
> > saveState/restoreState aren't called for server-side state saving.
> >
> > I'm cc'ing your message to the "MyFaces User mailing list"
> > <us...@myfaces.apache.org> as you're far more likely to get help there
> > than emailing me directly.
> >
>
>


--

http://www.irian.at

Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German

Professional Support for Apache MyFaces

Re: MyFaces Tomahawk

[Werner Punz <we...@gmx.at>]

Actually this seems either like a bug in the RI to me, since savestate
does nothing fancy which should not work in the RI. It basically just
does what every component does in the save and restore phase. Or a bug
by the user.

Maybe some of the classes in the original tree are not serializable,
which could cause a problem, due to the fact that the beans themselves
are serialized by saveState.



Mike Kienenberger schrieb:
> Rick,
> 
> Sorry.  I can't help you.   I've never used the JSF RI, nor do I use
> server-side state saving.
> 
> You could either implement the special phase listener described in 
> TOMAHAWK-134 or you could try asking on the JSF RI list why
> saveState/restoreState aren't called for server-side state saving.
> 
> I'm cc'ing your message to the "MyFaces User mailing list"
> <us...@myfaces.apache.org> as you're far more likely to get help there
> than emailing me directly.
>