Re: [VOTE] fix MYFACES-2552 for 2.0.x and 2.1.x branches

I agree STRICT_JSF_2_COMPATIBILITY is too generic. I think the param should contain EL, TYPE, MAP, RESOLVER, NULL. And it should enabled by default. Regards Bernd On Wed, Sep 21, 2011 at 11:50 PM, Mark Struberg strub...@yahoo.de wrote: Shouldnt the config contain the text EL_TYPE or so? We

Re: [VOTE] fix MYFACES-2552 for 2.0.x and 2.1.x branches

@bernd: +1 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/22 Bernd Bohmann bernd.bohm...@atanion.com I agree STRICT_JSF_2_COMPATIBILITY is too generic. I think the

Re: [VOTE] fix MYFACES-2552 for 2.0.x and 2.1.x branches

+1 in general, +1 to Bernd's suggestion. best regards, Martin On Thu, Sep 22, 2011 at 9:59 AM, Gerhard Petracek gerhard.petra...@gmail.com wrote: @bernd: +1 regards, gerhard http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German

[jira] [Commented] (MYFACES-1357) commandButton inside datatable doesn't process action

[ https://issues.apache.org/jira/browse/MYFACES-1357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13112412#comment-13112412 ] Ondrej Svetlik commented on MYFACES-1357: - 1. is your h:commandButton inside

Re: [VOTE] fix MYFACES-2552 for 2.0.x and 2.1.x branches

Hi, Both suggestions for a name are reasonable, because they suggest different things! What Leo suggested (STRICT_JSF_2_COMPATIBILITY), is the flag we (internally) have been discussing (and postponing) for a long time. This config parameter would enable us to include non-spec behavior in MyFaces

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 22.09.2011 12:16, schrieb Jakob Korherr: Hi, Both suggestions for a name are

Re: [VOTE] fix MYFACES-2552 for 2.0.x and 2.1.x branches

of course there is: http://myfaces.apache.org/core20/myfaces-impl/webconfig.html LieGrue, strub - Original Message - From: Michael Kurz michi.k...@gmx.at To: MyFaces Development dev@myfaces.apache.org Cc: Sent: Thursday, September 22, 2011 1:14 PM Subject: Re: [VOTE] fix

Re: [VOTE] fix MYFACES-2552 for 2.0.x and 2.1.x branches

OK, good. But: This would then be parameter 94 to consider? Best regards Michi Am 22.09.2011 13:17, schrieb Mark Struberg: of course there is: http://myfaces.apache.org/core20/myfaces-impl/webconfig.html LieGrue, strub - Original Message - From: Michael Kurzmichi.k...@gmx.at To:

Re: [VOTE] fix MYFACES-2552 for 2.0.x and 2.1.x branches

Sorry I suggested to enable this parameter as default You only need to know this parameter if you need the old behavoir Regards Bernd On Thu, Sep 22, 2011 at 1:30 PM, Michael Kurz michi.k...@gmx.at wrote: OK, good. But: This would then be parameter 94 to consider? Best regards Michi Am

[jira] [Created] (MYFACES-3314) AjaxBehavior.getStateHelper() should be protected

AjaxBehavior.getStateHelper() should be protected - Key: MYFACES-3314 URL: https://issues.apache.org/jira/browse/MYFACES-3314 Project: MyFaces Core Issue Type: Improvement

[jira] [Updated] (MYFACES-3314) AjaxBehavior.getStateHelper() should be protected

[ https://issues.apache.org/jira/browse/MYFACES-3314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Kurz updated MYFACES-3314: -- Status: Patch Available (was: Open) AjaxBehavior.getStateHelper() should be protected

Re: [VOTE] fix MYFACES-2552 for 2.0.x and 2.1.x branches

+1 :) Am 22.09.2011 um 14:15 schrieb Bernd Bohmann: Sorry I suggested to enable this parameter as default You only need to know this parameter if you need the old behavoir Regards Bernd On Thu, Sep 22, 2011 at 1:30 PM, Michael Kurz michi.k...@gmx.at wrote: OK, good. But: This would

Re: [VOTE] fix MYFACES-2552 for 2.0.x and 2.1.x branches

Hi Ok, so can we agree on use a name like org.apache.myfaces.STRICT_JSF_2_EL_RESOLVER_COMPATIBILITY? I strongly suggest the default value of this param should be false by the following reasons: 1. I don't believe the TCK check this specific part. Only if the change cause a test to fail, we are

Re: [VOTE] fix MYFACES-2552 for 2.0.x and 2.1.x branches

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.

[jira] [Updated] (TRINIDAD-2130) Skinning: support separate style sheets for secure + non-secure pages

[ https://issues.apache.org/jira/browse/TRINIDAD-2130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Schwartz updated TRINIDAD-2130: Status: Patch Available (was: Open) Skinning: support separate style sheets for

[jira] [Created] (MYFACES-3315) @FacesValidator.isDefault() not processed

@FacesValidator.isDefault() not processed - Key: MYFACES-3315 URL: https://issues.apache.org/jira/browse/MYFACES-3315 Project: MyFaces Core Issue Type: Bug Components: JSR-314 Affects

[jira] [Created] (MYFACES-3316) Problem concerning MyFaces-1890: does not work when dealing with a composite component

Problem concerning MyFaces-1890: does not work when dealing with a composite component -- Key: MYFACES-3316 URL: https://issues.apache.org/jira/browse/MYFACES-3316

[jira] [Created] (MYFACES-3317) Separate error name and error message

Separate error name and error message - Key: MYFACES-3317 URL: https://issues.apache.org/jira/browse/MYFACES-3317 Project: MyFaces Core Issue Type: Improvement Components: JSR-314

[jira] [Updated] (MYFACES-3317) Separate error name and error message in ajax message box

[ https://issues.apache.org/jira/browse/MYFACES-3317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leonardo Uribe updated MYFACES-3317: Status: Patch Available (was: Open) Separate error name and error message in ajax

[jira] [Created] (MYFACES-3318) Documentation for insert ajax command does not match with spec xsd

Documentation for insert ajax command does not match with spec xsd -- Key: MYFACES-3318 URL: https://issues.apache.org/jira/browse/MYFACES-3318 Project: MyFaces Core Issue

[jira] [Updated] (MYFACES-3318) Documentation for insert ajax command does not match with spec xsd

[ https://issues.apache.org/jira/browse/MYFACES-3318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leonardo Uribe updated MYFACES-3318: Status: Patch Available (was: Open) Documentation for insert ajax command does not

[jira] [Commented] (EXTCDI-228) Navigation with redirect isn't performed in combination with Trinidad 2 support module

[ https://issues.apache.org/jira/browse/EXTCDI-228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13113154#comment-13113154 ] Rudy De Busscher commented on EXTCDI-228: - With plain JSF, there is no issue. I

[jira] [Created] (EXTCDI-228) Navigation with redirect isn't performed in combination with Trinidad 2 support module

Navigation with redirect isn't performed in combination with Trinidad 2 support module -- Key: EXTCDI-228 URL: https://issues.apache.org/jira/browse/EXTCDI-228