Hi
Following the previous discussion about MYFACES-2552 (see this thread):
http://markmail.org/message/kreytqexrucair2k?q=%5BVOTE%5D+fix+MYFACES-2552+for+2%2E0%2Ex+and+2%2E1%2Ex+branches
I have attached a new patch ( MYFACES-2552-4.patch ) adding a param
called
+1
On Tue, Nov 8, 2011 at 8:01 PM, Leonardo Uribe lu4...@gmail.com wrote:
Hi
Following the previous discussion about MYFACES-2552 (see this thread):
http://markmail.org/message/kreytqexrucair2k?q=%5BVOTE%5D+fix+MYFACES-2552+for+2%2E0%2Ex+and+2%2E1%2Ex+branches
I have attached a new patch (
+1
Regards,
Jakob
2011/11/8 Bernd Bohmann bernd.bohm...@atanion.com:
+1
On Tue, Nov 8, 2011 at 8:01 PM, Leonardo Uribe lu4...@gmail.com wrote:
Hi
Following the previous discussion about MYFACES-2552 (see this thread):
: Matt Benson gudnabr...@gmail.com
To: MyFaces Development dev@myfaces.apache.org
Cc:
Sent: Wednesday, September 21, 2011 6:29 PM
Subject: Re: [VOTE] fix MYFACES-2552 for 2.0.x and 2.1.x
branches
+1
However, let's simplify the context parameter by giving it
a name
relating to JSF 2.2
,
strub
- Original Message -
From: Jakob Korherr jakob.korh...@gmail.com
To: MyFaces Development dev@myfaces.apache.org
Cc: gudnabr...@gmail.com
Sent: Wednesday, September 21, 2011 10:20 PM
Subject: Re: [VOTE] fix MYFACES-2552 for 2.0.x and 2.1.x branches
+1
Cc: gudnabr...@gmail.com
Sent: Wednesday, September 21, 2011 10:20 PM
Subject: Re: [VOTE] fix MYFACES-2552 for 2.0.x and 2.1.x branches
+1 for including the fix in 2.0.x and 2.1.x + adding
org.apache.myfaces.STRICT_JSF_2_COMPATIBILITY
Regards,
Jakob
2011/9/21 Leonardo Uribe lu4
-
From: Jakob Korherr jakob.korh...@gmail.com
To: MyFaces Development dev@myfaces.apache.org
Cc: gudnabr...@gmail.com
Sent: Wednesday, September 21, 2011 10:20 PM
Subject: Re: [VOTE] fix MYFACES-2552 for 2.0.x and 2.1.x branches
+1 for including the fix in 2.0.x and 2.1.x + adding
@myfaces.apache.org
Cc: gudnabr...@gmail.com
Sent: Wednesday, September 21, 2011 10:20 PM
Subject: Re: [VOTE] fix MYFACES-2552 for 2.0.x and 2.1.x branches
+1 for including the fix in 2.0.x and 2.1.x + adding
org.apache.myfaces.STRICT_JSF_2_COMPATIBILITY
Regards,
Jakob
2011/9/21 Leonardo Uribelu4
: [VOTE] fix MYFACES-2552
for 2.0.x and 2.1.x
branches
+1
However, let's simplify the
context parameter by giving it
a name
relating to JSF 2.2 compatibility. I
submitted the final
implementation for Mojarra, so have
every right to add the same
to
MyFaces
To: MyFaces Developmentdev@myfaces.apache.org
Cc:
Sent: Thursday, September 22, 2011 1:14 PM
Subject: Re: [VOTE] fix MYFACES-2552 for 2.0.x and 2.1.x branches
I agree with Jakob, nobody will know about a parameter like this (are
they documented anywhere btw?). The effect (without setting
1:14 PM
Subject: Re: [VOTE] fix MYFACES-2552 for 2.0.x and 2.1.x branches
I agree with Jakob, nobody will know about a parameter like this (are
they documented anywhere btw?). The effect (without setting it): for
application developers JSF seems to be broken.
Best regards
Michi
Am
Developmentdev@myfaces.apache.org
Cc:
Sent: Thursday, September 22, 2011 1:14 PM
Subject: Re: [VOTE] fix MYFACES-2552 for 2.0.x and 2.1.x branches
I agree with Jakob, nobody will know about a parameter like this (are
they documented anywhere btw?). The effect (without setting
:
Sent: Thursday, September 22, 2011 1:14 PM
Subject: Re: [VOTE] fix MYFACES-2552 for 2.0.x and 2.1.x branches
I agree with Jakob, nobody will know about a parameter like this (are
they documented anywhere btw?). The effect (without setting it): for
application developers JSF seems to be broken
Ok, so can we agree on use a name like
org.apache.myfaces.STRICT_JSF_2_EL_RESOLVER_COMPATIBILITY?--
I would say yes, so that it leaves space for possible
org.apache.myfaces.STRICT_JSF_* parameters in the future.
Grant Smith - V.P. Information Technology
Marathon Computer Systems, LLC.
+1
2011/9/21 Leonardo Uribe lu4...@gmail.com:
Hi
More than a year ago, it was found that EL expressions like
#{cc.attrs.test} does not resolve its type correctly, because the
composite component EL resolver is not able to find the right type.
Instead, MapELResolver always return
+1
Am 21.09.2011 um 14:20 schrieb Leonardo Uribe:
+1
2011/9/21 Leonardo Uribe lu4...@gmail.com:
Hi
More than a year ago, it was found that EL expressions like
#{cc.attrs.test} does not resolve its type correctly, because the
composite component EL resolver is not able to find the right
+1 if it's configurable in a context-param. How about
org.apache.myfaces.EL_RESOLVER_GETTYPE_RETURNS_NULL ?
On Wed, Sep 21, 2011 at 5:35 AM, Michael Kurz michi.k...@gmx.at wrote:
+1
Am 21.09.2011 um 14:20 schrieb Leonardo Uribe:
+1
2011/9/21 Leonardo Uribe lu4...@gmail.com:
Hi
+1
And if we create a context parameter, it should behave by default as in the
JSF 2.2 Spec. If users want strict spec (2.0/2.1)behaviour they have to set
the parameter value.
regards
Rudy
On 21 September 2011 17:08, Grant Smith work.gr...@gmail.com wrote:
+1 if it's configurable in a
+1 for it in combination with the context parameter
regards,
gerhard
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
2011/9/21 Rudy De Busscher rdebussc...@gmail.com
+1
And if we create a
+1
However, let's simplify the context parameter by giving it a name
relating to JSF 2.2 compatibility. I submitted the final
implementation for Mojarra, so have every right to add the same to
MyFaces.
Matt
On Wed, Sep 21, 2011 at 11:19 AM, Gerhard Petracek
gerhard.petra...@gmail.com wrote:
From: Grant Smith work.gr...@gmail.com
To: MyFaces Development dev@myfaces.apache.org
Sent: Wednesday, September 21, 2011 5:08 PM
Subject: Re: [VOTE] fix MYFACES-2552 for 2.0.x and 2.1.x branches
+1 if it's configurable in a context-param. How about
gudnabr...@gmail.com
To: MyFaces Development dev@myfaces.apache.org
Cc:
Sent: Wednesday, September 21, 2011 6:29 PM
Subject: Re: [VOTE] fix MYFACES-2552 for 2.0.x and 2.1.x branches
+1
However, let's simplify the context parameter by giving it a name
relating to JSF 2.2 compatibility. I
dev@myfaces.apache.org
Cc:
Sent: Wednesday, September 21, 2011 6:29 PM
Subject: Re: [VOTE] fix MYFACES-2552 for 2.0.x and 2.1.x branches
+1
However, let's simplify the context parameter by giving it a name
relating to JSF 2.2 compatibility. I submitted the final
implementation for Mojarra
LieGrue,
strub
- Original Message -
From: Matt Benson gudnabr...@gmail.com
To: MyFaces Development dev@myfaces.apache.org
Cc:
Sent: Wednesday, September 21, 2011 6:29 PM
Subject: Re: [VOTE] fix MYFACES-2552 for 2.0.x and 2.1.x branches
+1
However, let's simplify the context
@myfaces.apache.org
Cc:
Sent: Wednesday, September 21, 2011 6:29 PM
Subject: Re: [VOTE] fix MYFACES-2552 for 2.0.x and 2.1.x branches
+1
However, let's simplify the context parameter by giving it a name
relating to JSF 2.2 compatibility. I submitted the final
implementation for Mojarra, so have every
with javax
LieGrue,
strub
- Original Message -
From: Matt Benson gudnabr...@gmail.com
To: MyFaces Development dev@myfaces.apache.org
Cc:
Sent: Wednesday, September 21, 2011 6:29 PM
Subject: Re: [VOTE] fix MYFACES-2552 for 2.0.x and 2.1.x branches
+1
However
gudnabr...@gmail.com
To: MyFaces Development dev@myfaces.apache.org
Cc:
Sent: Wednesday, September 21, 2011 6:29 PM
Subject: Re: [VOTE] fix MYFACES-2552 for 2.0.x and 2.1.x branches
+1
However, let's simplify the context parameter by giving it a name
relating to JSF 2.2 compatibility
, September 21, 2011 10:20 PM
Subject: Re: [VOTE] fix MYFACES-2552 for 2.0.x and 2.1.x branches
+1 for including the fix in 2.0.x and 2.1.x + adding
org.apache.myfaces.STRICT_JSF_2_COMPATIBILITY
Regards,
Jakob
2011/9/21 Leonardo Uribe lu4...@gmail.com:
Hi
@Matt Benson: Could you attach
28 matches
Mail list logo
