Hi All,
Currently in orchestra there are two types of conversation scope: manual and
flash. With manual, a conversation must be explicitly ended via either a
call to the Orchestra API, or use of a jsf tag. With flash, the conversation
is automatically ended when a request cycle ends and no
Aargh.. top posting!
Simon
Regards,
I will try to find some time this weekend.
Yes, we would like to get a new release out in the next couple of weeks.
Hi Matthias,
Matthias Wessendorf [EMAIL PROTECTED] schrieb:
That sounds very good.
Do you guys plan to release the bits soon as
Hi Simon!
Are there any objections?
Sounds good!
Ciao,
Mario
That sounds very good.
Do you guys plan to release the bits soon as well ?
-M
On Jan 29, 2008 9:03 AM, Mario Ivankovits [EMAIL PROTECTED] wrote:
Hi Simon!
Are there any objections?
Sounds good!
Ciao,
Mario
--
Matthias Wessendorf
further stuff:
blog:
Yes, we would like to get a new release out in the next couple of weeks.
nice
Hi Matthias,
bonjourno
Matthias Wessendorf [EMAIL PROTECTED] schrieb:
That sounds very good.
Do you guys plan to release the bits soon as well ?
-M
On Jan 29, 2008 9:03 AM, Mario Ivankovits
yes, good idea
+1
I like the name access scope and also experienced people who use the
term flash scope for t:saveState usage.
--Manfred
On Jan 29, 2008 8:59 AM, Simon Kitching [EMAIL PROTECTED] wrote:
Hi All,
Currently in orchestra there are two types of conversation scope: manual
and
will there be a flash scope in Orchestra as well (as an option to using
t:saveState)?
will Trinidad ever be fixed to work with a flash-scope ;) ?
regards,
Martin
On Jan 29, 2008 12:25 PM, Manfred Geiler [EMAIL PROTECTED] wrote:
yes, good idea
+1
I like the name access scope and also
then maybe it should be named page-scope
:-)
will Trinidad ever be fixed to work with a flash-scope ;) ?
I was referring to the fact that Trinidad does not work with t:saveState,
due to the optimized state-saving. I wonder if this can/should be fixed at
some point of time.
ah,
Hi Matthias,
from the commits looks like flash will be the alias for access
then maybe it should be named page-scope
will Trinidad ever be fixed to work with a flash-scope ;) ?
I was referring to the fact that Trinidad does not work with t:saveState,
due to the optimized state-saving. I
On Jan 29, 2008 1:22 PM, Martin Marinschek [EMAIL PROTECTED] wrote:
will there be a flash scope in Orchestra as well (as an option to using
t:saveState)?
from the commits looks like flash will be the alias for access
will Trinidad ever be fixed to work with a flash-scope ;) ?
I moved all my
://www.JSFCentral.com - JavaServer Faces FAQ, news, and info
-Original Message-
From: Simon Kitching [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 29, 2008 3:00 AM
To: dev@myfaces.apache.org
Subject: [orchestra] rename scope flash to access
Hi All,
Currently in orchestra
consulting, training, and mentoring
http://www.JSFCentral.com - JavaServer Faces FAQ, news, and info
-Original Message-
From: Simon Kitching [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 29, 2008 3:00 AM
To: dev@myfaces.apache.org
Subject: [orchestra] rename scope flash to access
Hi!
Hmmm... I agree that flash can be misleading, but access doesn't seem very descriptive to me. I
think page or view might be more appropriate.
As it is currently in Orchestra, the fomer flash-scope is exactly an
access-scope. As long as the bean is accessed it stay alive, regardles
of
13 matches
Mail list logo
