, November 30, 2012 5:47 AM
Subject: Re: CODI: Exclude windowId from certain pages
Hi
Are you invalidating the session (logout) in some point? Maybe that
could be
related to the problem, because if you keep the session active and
create
hundreds of different windows, since
well tested imo.
LieGrue,
strub
- Original Message -
From: Leonardo Uribe lu4...@gmail.com
To: MyFaces Discussion users@myfaces.apache.org
Cc:
Sent: Friday, November 30, 2012 5:47 AM
Subject: Re: CODI: Exclude windowId from certain pages
Hi
Are you invalidating
kaiser.andr...@gmail.com
To: MyFaces Discussion users@myfaces.apache.org
Sent: Friday, November 30, 2012 10:24 AM
Subject: Re: CODI: Exclude windowId from certain pages
Hi
thanks for all answers. I will try to reduce the number of windows per
session.
Also i will try to change my stress test script
,
Leonardo Uribe
LieGrue,
strub
From: Andreas Kaiser kaiser.andr...@gmail.com
To: MyFaces Discussion users@myfaces.apache.org
Sent: Friday, November 30, 2012 10:24 AM
Subject: Re: CODI: Exclude windowId from certain pages
Hi
thanks for all answers. I
hi andreas,
first of all: welcome @ myfaces!
there are different approaches - e.g. you can use urls with
windowId=automatedEntryPoint
(see the javadoc in WindowContextManager)
regards,
gerhard
http://www.irian.at
Your JSF/JavaEE powerhouse -
JavaEE Consulting, Development and
Courses in
Hi
thanks for the answer
I will have a look at this.
BTW. it seems that the the windowId is a potential security issue.
For instance call a side with an unknown windowId. CODI will generate a new
valid one. Just change the generated one to a new invalid id. CODI will
generate a new one again.
hi andreas,
please have a look at WindowContextConfig - see e.g.
#isUnknownWindowIdsAllowed and #getMaxWindowContextCount
- it shouldn't be an issue (since you can customize the default behaviour).
btw:
we are doing a lot of such tests (without windowId=automatedEntryPoint) and
never saw an
Hi
Are you invalidating the session (logout) in some point? Maybe that could be
related to the problem, because if you keep the session active and create
hundreds of different windows, since the session is not released that memory
will not be restored and the stress testing will not be accurate
I think I've seen this discussed in this forum within the last few months
(I might be wrong though).
Anyway, I remember a similar topic and a solution, but it wasn't a CODI
solution; this may or may not be related/solution.
Quote from http://stackoverflow.com/a/5475564/933054
*Until what point
Hi
MyFaces has two web config params to limit the number of views in session:
org.apache.myfaces.NUMBER_OF_VIEWS_IN_SESSION (default 20)
org.apache.myfaces.NUMBER_OF_SEQUENTIAL_VIEWS_IN_SESSION
With the improvements done in MyFaces over PSS algorithm , there is no
need to worry about the view
tested imo.
LieGrue,
strub
- Original Message -
From: Leonardo Uribe lu4...@gmail.com
To: MyFaces Discussion users@myfaces.apache.org
Cc:
Sent: Friday, November 30, 2012 5:47 AM
Subject: Re: CODI: Exclude windowId from certain pages
Hi
Are you invalidating the session (logout
Discussion users@myfaces.apache.org
Cc:
Sent: Friday, November 30, 2012 5:47 AM
Subject: Re: CODI: Exclude windowId from certain pages
Hi
Are you invalidating the session (logout) in some point? Maybe that
could be
related to the problem, because if you keep the session active and create
12 matches
Mail list logo
