Mailing-List: contact deltaspike-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: deltaspike-dev@incubator.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.de;
  h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding;
  b=Wcp+XXJ0SIGuZlWS4BYvugdLExeDpbxcvJW8/IlAAxiGjPhZcyOa1CtC6imy5Lk+FjFwDCzHjuHrGYDLBHAUVyEpE+yHCecEZ+VZgOFdf8dmFqzJMmrUC/f9onGQRV7qO1Z3bwFyykAVqEvfepe3aeY+VZo4zsrIWOptJW86tY4=;
References: <1350287721.87777.YahooMailNeo@web28906.mail.ir2.yahoo.com>
 <CAGJtJfGC7wcvG81iXy6VB=wdri7Xoad52ko_=rdyms3t6QD_MQ@mail.gmail.com>
 <1350292357.66134.YahooMailNeo@web28903.mail.ir2.yahoo.com>
 <CAGJtJfGoVQe43rUZkBh0yFGpsMeP14-KER1wPoaFpBdbs6xiTQ@mail.gmail.com>
 <1350294764.2070.YahooMailNeo@web28904.mail.ir2.yahoo.com>
 <CAL+wt-6oLtOiUAPKSRVjZbc3QyfxfdvmJX5kWs-3yJJhduq71A@mail.gmail.com>
Message-ID: <1350296915.49081.YahooMailNeo@web28904.mail.ir2.yahoo.com>
Date: Mon, 15 Oct 2012 11:28:35 +0100 (BST)
From: Mark Struberg <struberg@yahoo.de>
Reply-To: Mark Struberg <struberg@yahoo.de>
Subject: Re: [DISCUSS] JSF Scopes
To: "deltaspike-dev@incubator.apache.org"
 <deltaspike-dev@incubator.apache.org>
In-Reply-To: 
 <CAL+wt-6oLtOiUAPKSRVjZbc3QyfxfdvmJX5kWs-3yJJhduq71A@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

Yes, this is definitely on our list. Indeed @ViewAccessScoped is one of the=
 most loved features of CODI.=0A=0ATo all others a quick explanation what C=
ODIs @ViewAccessScoped does. It basically keeps your bean alive until you d=
o NOT use it on a page anymore. This is kind of an auto-conversation which =
expires if you hit a page which doesnt need that bean anymore. At the next =
time you hit that page you will get a fresh contextual instance of that ver=
y bean.=0A=0A=0ALieGrue,=0Astrub=0A=0A=0A=0A----- Original Message -----=0A=
> From: Rudy De Busscher <rdebusscher@gmail.com>=0A> To: deltaspike-dev@inc=
ubator.apache.org=0A> Cc: =0A> Sent: Monday, October 15, 2012 12:17 PM=0A> =
Subject: Re: [DISCUSS] JSF Scopes=0A> =0A> All,=0A> =0A> Is ViewAccessScope=
d of CODI considered.=A0 For me the most important non std=0A> scope.=0A> =
=0A> regards=0A> Rudy=0A> =0A> =0A> On 15 October 2012 11:52, Mark Struberg=
 <struberg@yahoo.de> wrote:=0A> =0A>>  I don't understand. The FacesMessage=
s are held by the FacesContext.=0A>> =0A>>  If we talk about a WindowContex=
t we always have to distinguish between the=0A>>  list of active window con=
texts and the 1 which is active for the current=0A>>  request.=0A>> =0A>>  =
LieGrue,=0A>>  strub=0A>> =0A>> =0A>> =0A>> =0A>>  ----- Original Message -=
----=0A>>  > From: Gerhard Petracek <gerhard.petracek@gmail.com>=0A>>  > To=
: deltaspike-dev@incubator.apache.org=0A>>  > Cc:=0A>>  > Sent: Monday, Oct=
ober 15, 2012 11:26 AM=0A>>  > Subject: Re: [DISCUSS] JSF Scopes=0A>>  >=0A=
>>  >t hat isn't correct. i thought about that as well, but some people =0A=
> use it=0A>>  > instead of std. cdi conversations to get rid of the disadv=
antages.=0A>>  > -> if you would close (or restart) the window-scope and yo=
u =0A> don't have an=0A>>  > independent window-context, you would lose the=
 information stored for =0A> the=0A>>  > current window (like faces-message=
s you need in case of a redirect).=0A>>  >=0A>>  > regards,=0A>>  > gerhard=
=0A>>  >=0A>>  >=0A>>  >=0A>>  > 2012/10/15 Mark Struberg <struberg@yahoo.d=
e>=0A>>  >=0A>>  >>=A0 Well, the Window Context is just the backing for @Wi=
ndowScoped. =0A> We=0A>>  should=0A>>  >>=A0 try to not overengineer things=
.=0A>>  >>=0A>>  >>=A0 All the Conversation scopes are based on the WindowC=
ontext.=0A>>  >>=A0 We should definitely get @ViewAccessScoped as this is s=
omething =0A> most=0A>>  users=0A>>  >>=A0 really love.=0A>>  >>=A0 But I'm=
 sure there is also quite some interesting stuff in =0A> Seam3 we=0A>>  > s=
hould=0A>>  >>=A0 look at.Thanks Antoine so far for the start.=A0 Anything =
missing in =0A> his=0A>>  list?=0A>>  >>=0A>>  >>=A0 LieGrue,=0A>>  >>=A0 s=
trub=0A>>  >>=0A>>  >>=0A>>  >>=0A>>  >>=0A>>  >>=A0 ----- Original Message=
 -----=0A>>  >>=A0 > From: Gerhard Petracek <gerhard.petracek@gmail.com>=0A=
>>  >>=A0 > To: deltaspike-dev@incubator.apache.org=0A>>  >>=A0 > Cc:=0A>> =
 >>=A0 > Sent: Monday, October 15, 2012 11:00 AM=0A>>  >>=A0 > Subject: Re:=
 [DISCUSS] JSF Scopes=0A>>  >>=A0 >=0A>>  >>=A0 > imo we should create:=0A>=
>  >>=A0 > - a client-window adapter (as spi) for a 1:1 delegation to =0A> =
the=0A>>  >>=A0 > client-window-api of jsf 2.2+=0A>>  >>=A0 > - a client-wi=
ndow implementation for jsf 2.0 and 2.1=0A>>  >>=A0 > - a window-context si=
milar to what we have in codi (that =0A> isn't the=0A>>  >>=A0 > window-sco=
pe - see [1])=0A>>  >>=A0 > - scopes + a fine grained api to manage them (t=
he =0A> window-scope is=0A>>  also=0A>>  >>=A0 just=0A>>  >>=A0 > a kind of=
 conversation which is very similar to std. cdi=0A>>  > conversations).=0A>=
>  >>=A0 >=0A>>  >>=A0 > we could think about a more specialized spi per sc=
ope (since =0A> we saw=0A>>  > that=0A>>  >>=A0 > some edge-cases with the =
ViewAccessScoped required internal=0A>>  > workarounds)=0A>>  >>=A0 > and w=
e could skip some SPIs for now.=0A>>  >>=A0 >=0A>>  >>=A0 > the first step =
is an agreement about the api, spi and the =0A> basic=0A>>  > behavior.=0A>=
>  >>=A0 >=0A>>  >>=A0 > regards,=0A>>  >>=A0 > gerhard=0A>>  >>=A0 >=0A>> =
 >>=A0 > [1]=0A>>  >>=A0 >=0A>>  >>=0A>>  >=0A>> =0A> https://cwiki.apache.=
org/confluence/display/EXTCDI/JSF+Usage#JSFUsage-Scopes=0A>>  >>=A0 >=0A>> =
 >>=A0 >=0A>>  >>=A0 >=0A>>  >>=A0 > 2012/10/15 Mark Struberg <struberg@yah=
oo.de>=0A>>  >>=A0 >=0A>>  >>=A0 >>=A0 Hi folks!=0A>>  >>=A0 >>=0A>>  >>=A0=
 >>=A0 I finally like to start working on JSF scopes for =0A> DeltaSpike.=
=0A>>  >>=A0 >>=0A>>  >>=A0 >>=A0 We already have the following 2 features =
implemented =0A> and working=0A>>  >>=A0 >>=A0 (including unit tests):=0A>>=
  >>=A0 >>=0A>>  >>=A0 >>=A0 * JFS @ViewScoped Context support=0A>>  >>=A0 =
>>=A0 * JSF-2-CDI scope mapping.=0A>>  >>=A0 >>=A0 * injecting typesafe JSF=
 messages=0A>>  >>=A0 >>=0A>>  >>=A0 >>=0A>>  >>=A0 >>=A0 The next item on =
my list is the=0A>>  >>=A0 >>=0A>>  >>=A0 >>=A0 * @WindowScoped=0A>>  >>=A0=
 >>=0A>>  >>=A0 >>=0A>>  >>=A0 >>=A0 This is kind of a Session per browser =
tab. Does Seam3 =0A> provide a=0A>>  > similar=0A>>  >>=A0 >>=A0 mechanism?=
 If not, I suggest taking a peak what we do =0A> over in=0A>>  > CODI.=0A>>=
  >>=A0 >>=A0 There is quite some trickery necessary, but we finally =0A> f=
ound a=0A>>  > solution=0A>>  >>=A0 >>=A0 which works pretty well [1]. This=
 is also the base of =0A> the=0A>>  > windowId=0A>>  >>=A0 feature=0A>>  >>=
=A0 >>=A0 most probably coming with JSF-2.2 btw.=0A>>  >>=A0 >>=0A>>  >>=A0=
 >>=0A>>  >>=A0 >>=A0 Once we have the @WindowScoped support we can build =
=0A> much more=0A>>  > fine=0A>>  >>=A0 grained=0A>>  >>=A0 >>=A0 conversat=
ion stuff which is perfectly browser tab aware =0A> based on=0A>>  > it.=0A=
>>  >>=A0 >>=0A>>  >>=A0 >>=0A>>  >>=A0 >>=A0 Wdyt?=0A>>  >>=A0 >>=0A>>  >>=
=A0 >>=A0 Any cool features related to this to look at in Seam3?=0A>>  >>=
=A0 >>=A0 Who is interested to help hacking this stuff?=0A>>  >>=A0 >>=0A>>=
  >>=A0 >>=0A>>  >>=A0 >>=A0 LieGrue,=0A>>  >>=A0 >>=A0 strub=0A>>  >>=A0 >=
>=0A>>  >>=A0 >>=0A>>  >>=A0 >>=0A>>  >>=A0 >>=A0 [1]=0A>>  >>=A0 =0A> http=
s://cwiki.apache.org/confluence/display/EXTCDI/JSF+WindowHandler=0A>>  >>=
=A0 >>=0A>>  >>=A0 >>=0A>>  >>=A0 >=0A>>  >>=0A>>  >=0A>> =0A>