Hello. Does anybody have any input on this? It seems like I'm
pretty close to get this sorted out, and a nudge in the right direction
would be a big help.
Thanks...
Dave
________________________________
From: David Brunette
Sent: Thursday, November 08, 2007 1:21 PM
To: [email protected]; [EMAIL PROTECTED]
Subject: [Trinidad][Facelets] CACHE_VEW_ROOT=false and
BUILD_BEFORE_RESTORE=true
Hi all.
I'm having trouble trying to use
org.apache.myfaces.trinidad.CACHE_VIEW_ROOT=false together with
facelets.BUILD_BEFORE_RESTORE=true. I'm getting a NullPointerException
in Trinidad's StateManagerImpl.restoreView(). I've debugged that class
and I see where the exception is being through, but in trying to figure
out what's going on I need a little help understanding who/what is
responsible for restoring the view and its state when
CACHE_VIEW_ROOT=false and BUILD_BEFORE_RESTORE=true?:
1) If BUILD_BEFORE_RESTORE=false, then Trinidad's StateManagerImpl will
have the Structure, with which it can re-create the view. After it is
created, the StateManagerImpl can restore its state (by calling
root.processRestoreState()). Seems straight forward. Am I reading that
correctly?
2) If BUILD_BEFORE_RESTORE=true, I'm getting the NullPointerException
described above. But how can the Trinidad StateManagerImpl re-create
the view with no Structure? To me, it looks like that has to be done by
FaceletsViewHandler.buildView(). OK... but then how does the state get
applied to the components after buildView() is called?
In an effort to reduce the size of our session, I've stumbled
across this parameter (BUILD_BEFORE_RESTORE). It seems to reduce the
size rather significantly, and if I can get my app to function properly
with it, I think it would be great. Any info/direction I can get on
this is much appreciated.
Thanks...
Dave
The information transmitted herewith is sensitive information of Chordiant
Software or its customers and is intended only for use to the individual or
entity to which it is addressed. If the reader of this message is not the
intended recipient, you are hereby notified that any review, retransmission,
dissemination, distribution, copying or other use of, or taking of any action
in reliance upon, this information is strictly prohibited. If you have received
this communication in error, please contact the sender and delete the material
from your computer.
