I checked the work done in there and Imo this is far from usable. Let's get the
windowId right in 2.2 an backport it later.
It doesn't make any sense to have 2 branches to do try error in this area. To
stress your butterfly analogy: there is a difference between a cocoon and a
hydra ;)
My understanding is that there was no 2.2 to work in when this branch
was started.
The idea was to get it right in 2.1 in our proprietary
implementation, and then use that to insure that the 2.2 spec worked
in practice as well as in theory.
On Fri, Nov 16, 2012 at 3:20 AM, Mark Struberg
- Original Message -
From: Mike Kienenberger mkien...@gmail.com
To: MyFaces Development dev@myfaces.apache.org; Mark Struberg
strub...@yahoo.de
Cc:
Sent: Friday, November 16, 2012 1:55 PM
Subject: Re: 2.1-windowId branch
My understanding is that there was no 2.2 to work in when this branch
and if it looks ok port it over to 2.1.x
LieGrue,
strub
- Original Message -
From: Mike Kienenberger mkien...@gmail.com
To: MyFaces Development dev@myfaces.apache.org; Mark Struberg
strub...@yahoo.de
Cc:
Sent: Friday, November 16, 2012 1:55 PM
Subject: Re: 2.1-windowId branch
My
, 2012 4:40 PM
Subject: Re: 2.1-windowId branch
Hi
Really the advantage to work in 2.1.x-client-window is if people is
working in 2.2.x, there are chances that by some commit, the code gets
unstable for some time. Since 2.1.x-client-window is JSF 2.1 + client
window api does not contain
to 2.1.x
LieGrue,
strub
- Original Message -
From: Leonardo Uribe lu4...@gmail.com
To: MyFaces Development dev@myfaces.apache.org; Mark Struberg
strub...@yahoo.de
Cc:
Sent: Friday, November 16, 2012 4:40 PM
Subject: Re: 2.1-windowId branch
Hi
Really the advantage to work
Struberg
strub...@yahoo.de
Cc:
Sent: Friday, November 16, 2012 4:40 PM
Subject: Re: 2.1-windowId branch
Hi
Really the advantage to work in 2.1.x-client-window is if people is
working in 2.2.x, there are chances that by some commit, the code gets
unstable for some time. Since 2.1.x
