[jira] Resolved: (EXTCDI-79) introduce client side windowhandler

[ https://issues.apache.org/jira/browse/EXTCDI-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakob Korherr resolved EXTCDI-79. - Resolution: Fixed Fix Version/s: 0.9.1 ClientSideWindowHandler works perfectly if

[jira] Commented: (MYFACES-2949) I think that MyFaces should use JSF 2 resource handling instead of directly write script resources to the output stream

[ https://issues.apache.org/jira/browse/MYFACES-2949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12966641#action_12966641 ] Leonardo Uribe commented on MYFACES-2949: - I checked this one and myfaces is

[jira] Resolved: (MYFACES-2985) Viewscoped bean does not get destroyed when navigating with faces-redirect to a non-jsf-page

[ https://issues.apache.org/jira/browse/MYFACES-2985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leonardo Uribe resolved MYFACES-2985. - Resolution: Fixed Fix Version/s: 2.0.3-SNAPSHOT Assignee: Leonardo

[jira] Created: (TRINIDAD-1969) RequestContext.getPartialTargets(UIComponent) is not context safe

RequestContext.getPartialTargets(UIComponent) is not context safe - Key: TRINIDAD-1969 URL: https://issues.apache.org/jira/browse/TRINIDAD-1969 Project: MyFaces Trinidad Issue

Possible problem in FacesConfig ordering

I'm finding a tck problem around FacesConfig ordering. I haven't figured out if this is caused by the geronimo integration or myfaces itself but I think there's something odd in the myfaces code. DefaultFacesConfigurationProvider line 461 has

[jira] Created: (MYFACES-2994) faces-config.xml referenced in webAppConfig absolute-ordering could not be on the classpath

faces-config.xml referenced in webAppConfig absolute-ordering could not be on the classpath - Key: MYFACES-2994 URL: https://issues.apache.org/jira/browse/MYFACES-2994

Re: Possible problem in FacesConfig ordering

Hi It is possible there is no faces-config.xml with the name configured in the webAppConfig. In theory, we can safely ignore it and a simple check for null can do the job. I committed the fix on MYFACES-2994. regards, Leonardo Uribe 2010/12/3 David Jencks david_jen...@yahoo.com I'm finding

[jira] Resolved: (MYFACES-2994) faces-config.xml referenced in webAppConfig absolute-ordering could not be on the classpath

[ https://issues.apache.org/jira/browse/MYFACES-2994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leonardo Uribe resolved MYFACES-2994. - Resolution: Fixed Fix Version/s: 2.0.3-SNAPSHOT faces-config.xml referenced in

[jira] Commented: (MYFACES-2994) faces-config.xml referenced in webAppConfig absolute-ordering could not be on the classpath

[ https://issues.apache.org/jira/browse/MYFACES-2994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12966717#action_12966717 ] Leonardo Uribe commented on MYFACES-2994: - It is possible there is no

[jira] Resolved: (TRINIDAD-1967) DateTimeRangeValidator gives false failure if server specifies timezone attribute or timezone specified in trinidad-config.xml

[ https://issues.apache.org/jira/browse/TRINIDAD-1967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabrielle Crawford resolved TRINIDAD-1967. -- Resolution: Fixed Fix Version/s: 2.0.0.4-core