Hi Joachim,
The pageFlowScope is *the* alternative for t:savestate. I don't see why
pageFlowScope is less convenient. I admit you'll have to get used to it. But
in the end, I think pageFlowScope is a more structural solution. And
pageFlowScope is more versatile, as it can be used across pages
hey,
Is it possible that when we explicitly removed the mention of state saving
mechanism from web.xml configuration; that every component library is
choosing its own default rather and that could be causing things correctly?
here is my take at it:
1. state saving configured to client--
Hi,
I know Trinidad components use a special way of client side state saving.
Maybe the problem is that the Tomahawk components do not support this
Trinidad-specific solution. So it could be related to the fact that you're
mixing Tomahawk and Trinidad components, as you suggested.
Why are you
I also have the same experience with this problem.
Switching from state_saving_method from server to client (trinidad
token), on every action where navigation is null (probably something to
do with component tree not rebuilding), most non JSF tags are
duplicating on every request.
For
@myfaces.apache.org;
Subject: Re: [TRINIDAD] Header rendering multiple times.
I also have the same experience with this problem.
Switching from state_saving_method from server to client (trinidad
token), on every action where navigation is null (probably something to
do with component tree
Ooooh!
I'll have to check but if that works then it's a work-around for some of my
use-cases where this bug is really biting me in the arse...
Now if only I could convince the template authors that we have to use to
replace tomahawk components with trinidad only components...
-Stephen
On 15
Bart Kummel wrote:
Hello,
Why are you mixing Tomahawk and Trinidad components? Apart from some special
cases (e.g. captcha and schedule) there are Trinidad alternatives to every
Tomahawk component.
What do you use as the Trinidad replacement for t:savestate, as a
method to cache
.
-Original message-
From: Luka Surija l...@iytim.hr
Sent: Tue 16-03-2010 12:18
To: MyFaces Discussion users@myfaces.apache.org;
Subject: Re: [TRINIDAD] Header rendering multiple times.
I also have the same experience with this problem.
Switching from state_saving_method from server to client
Hi,
i'm not using any other components beside Trinidad
Luka Surija
Bart Kummel wrote:
Hi,
I know Trinidad components use a special way of client side state saving.
Maybe the problem is that the Tomahawk components do not support this
Trinidad-specific solution. So it could be related to the
There are no JSTL components being used.
Though we use facelets.
There is an entry in web.xml file :
context-param
param-namejavax.faces.STATE_SAVING_METHOD/param-name
param-valueclient/param-value
!--param-valueserver/param-value--
/context-param
When this entry is
Sorry, not sure then, anyone else have an idea?
-A
On Mon, Mar 15, 2010 at 6:11 AM, preeti agarwal
preetiagarwa...@gmail.com wrote:
There are no JSTL components being used.
Though we use facelets.
There is an entry in web.xml file :
context-param
Can anyone help in this issue?
On Mon, Mar 15, 2010 at 9:56 PM, Andrew Robinson
andrew.rw.robin...@gmail.com wrote:
Sorry, not sure then, anyone else have an idea?
-A
On Mon, Mar 15, 2010 at 6:11 AM, preeti agarwal
preetiagarwa...@gmail.com wrote:
There are no JSTL components being
Description of problem : I have an xhtml page in which I use trininad
components (like tablelayout) and also tomahawk components (like form). I
have used some usual HTML components along with it. First time the page is
rendered correctly. But anysubsequent refresh causes the header to render
Do you use any JSTL tags?
Have you any component binding in the page, especially ones that may
live longer than one request?
On Tue, Mar 9, 2010 at 7:31 AM, preeti agarwal
preetiagarwa...@gmail.com wrote:
Description of problem : I have an xhtml page in which I use trininad
components (like
14 matches
Mail list logo
