Hi
I have created the following branch:
http://svn.apache.org/repos/asf/myfaces/core/branches/2.1.x-client-window/
And committed an implementation of JSF 2.2 early draft api for
windowId, as suggested. The patch is available too in MYFACES-3588.
Inside the branch I created a simple test
Hi
2012/7/31 Gerhard Petracek gerhard.petra...@gmail.com:
hi leo,
no - we don't need a compromise just for testing this feature. it's really
an important feature also for v2.0.x and v2.1.x!
i explained all the advantages (for users of myfaces-core v2.0.x and v2.1.x
and also tomee) in the
hi leo,
since the goal is that the myfaces specific api should be aligned with the
jsf 2.2 api, the only difference should be the package and the lookup e.g.
of ClientWindow
- there isn't a big difference at all. which means in return: there's also
no issue with starting with the jsf 2.2 api -
+1
On Wed, Aug 1, 2012 at 4:05 PM, Gerhard Petracek
gerhard.petra...@gmail.com wrote:
hi leo,
since the goal is that the myfaces specific api should be aligned with the
jsf 2.2 api, the only difference should be the package and the lookup e.g.
of ClientWindow
- there isn't a big difference
hi leo,
i'm not sure if we really need such releases.
if it is easier for you to start with the official api of v2.2 and to
backport it afterwards, it's imo also ok to create a branch for it.
in this case we might have to drop (or refactor) this branch later on,
because the final ClientWindow
Hi Gerhard
In my opinion, start with 2.1.x is the wrong way to do it. Sounds
better to create a branch, do the necessary changes (including modify
javax.faces.* classes to match the spec draft, but only the necessary
for windowId feature), and then if that is not enough do the backport.
The
hi leo,
no - we don't need a compromise just for testing this feature. it's really
an important feature also for v2.0.x and v2.1.x!
i explained all the advantages (for users of myfaces-core v2.0.x and v2.1.x
and also tomee) in the first mail of this thread - please read it again.
if you have
Hi
There is an alternative to do it for 2.0.x / 2.1.x . We can create a
temporal 2.2.x branch that will only contain JSF 2.1 + JSF 2.2
windowId API and then we do milestones releases, which does not
require to be official (no TCK), with some additional identifier. For
example
hi @ all,
if there are no objections, i'll create a jira ticket for it tomorrow.
regards,
gerhard
http://www.irian.at
Your JSF/JavaEE powerhouse -
JavaEE Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
2012/7/20 David Blevins
From: Gerhard Petracek gpetra...@apache.org
To: MyFaces Development dev@myfaces.apache.org
Sent: Wednesday, July 18, 2012 7:13 PM
Subject: [DISCUSS] [Core] window-id for myfaces-core 2.0.x and 2.1.x
hi @ all,
you might know that jsf 2.2 will introduce
,
strub
From: Gerhard Petracek gpetra...@apache.org
To: MyFaces Development dev@myfaces.apache.org
Sent: Wednesday, July 18, 2012 7:13 PM
Subject: [DISCUSS] [Core] window-id for myfaces-core 2.0.x and 2.1.x
hi @ all,
you might know that jsf 2.2 will introduce
dev@myfaces.apache.org
Sent: Wednesday, July 18, 2012 7:13 PM
Subject: [DISCUSS] [Core] window-id for myfaces-core 2.0.x and 2.1.x
hi @ all,
you might know that jsf 2.2 will introduce ClientWindow (= window-id).
besides the basic multi-tab handling (separation), it also allows to fix
On Jul 19, 2012, at 2:49 AM, Mark Struberg wrote:
The internal API will be 1:1 sync with the proposed javax.faces API - we are
just not allowed to do it directly in javax.faces before it's official.
Sounds great. Only reason I ask was the TCK gets cranky when you change the
API signatures.
hi @ all,
you might know that jsf 2.2 will introduce ClientWindow (= window-id).
besides the basic multi-tab handling (separation), it also allows to fix
state-saving (- also view-scope) as well as the flash-scope for
multi-tab/window constellations.
since it's an important topic, we should
, July 18, 2012 7:13 PM
Subject: [DISCUSS] [Core] window-id for myfaces-core 2.0.x and 2.1.x
hi @ all,
you might know that jsf 2.2 will introduce ClientWindow (= window-id).
besides the basic multi-tab handling (separation), it also allows to fix
state-saving (- also view-scope) as well
: Wednesday, July 18, 2012 7:13 PM
Subject: [DISCUSS] [Core] window-id for myfaces-core 2.0.x and 2.1.x
hi @ all,
you might know that jsf 2.2 will introduce ClientWindow (= window-id).
besides the basic multi-tab handling (separation), it also allows to fix
state-saving (- also view-scope) as well
in the spec tracker since 2004 now ;)
LieGrue,
strub
From: Gerhard Petracek gpetra...@apache.org
To: MyFaces Development dev@myfaces.apache.org
Sent: Wednesday, July 18, 2012 7:13 PM
Subject: [DISCUSS] [Core] window-id for myfaces-core 2.0.x and 2.1.x
hi
17 matches
Mail list logo
