[ http://jira.jboss.com/jira/browse/RF-1255?page=all ] Nick Belaevski updated RF-1255: ------------------------------- Fix Version/s: 3.2.0 Assignee: Alexander Smirnov -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/RF-1255?page=all ] Nick Belaevski updated RF-1255: ------------------------------- Description: When the Richfaces 3.1.2 libs are put into a domains lib folder under SJSAS 9.1, the Admin web application breaks. I filed a bug report on glassfish https://glassfish.dev.java.net/issues/show_bug.cgi?id=3626 , here's what they had to say about this: "In order to understand what is happening you have to know a little bit about how JSF configures itself. It looks for faces-config.xml files in the classpath to see if should add new jsf extensions (such as a new ViewHandler) to help it process jsf pages. JSF does NOT do anything to ensure that a new component (i.e. ViewHanler) doesn't break other custom jsf extensions. It is unfortunate that these extensions can't be restricted to a subset of URLs, or be guarenteed to behave well. In this case, Ajax4JSF does not behave well. It both of your stack traces it appears Ajax4JSF is not doing the right thing. In the first, it is not handling the rendering of the page and has either changed the viewId or done something else to cause the default viewHandler to also not handle it (it appears it is redispatching recursively b/c of this). In the 2nd example, it is attempting to handle a JSFTemplating page instead of delegating to JSFTemplating -- it is unable to do so and fails. Ajax4JSF could fix both of these problems -- I cannot. Based on these stack traces, I would strongly suggest that you not include Ajax4JSF in a shared lib area as it will effect ALL JSF applications, not just the ones you want it to effect. Instead place the Ajax4JSF jar files in the WEB-INF/lib of your application(s)." was: When the Richfaces 3.1.2 libs are put into a domains lib folder under SJSAS 9.1, the Admin web application breaks. I filed a bug report on glassfish https://glassfish.dev.java.net/issues/show_bug.cgi?id=3626, here's what they had to say about this: "In order to understand what is happening you have to know a little bit about how JSF configures itself. It looks for faces-config.xml files in the classpath to see if should add new jsf extensions (such as a new ViewHandler) to help it process jsf pages. JSF does NOT do anything to ensure that a new component (i.e. ViewHanler) doesn't break other custom jsf extensions. It is unfortunate that these extensions can't be restricted to a subset of URLs, or be guarenteed to behave well. In this case, Ajax4JSF does not behave well. It both of your stack traces it appears Ajax4JSF is not doing the right thing. In the first, it is not handling the rendering of the page and has either changed the viewId or done something else to cause the default viewHandler to also not handle it (it appears it is redispatching recursively b/c of this). In the 2nd example, it is attempting to handle a JSFTemplating page instead of delegating to JSFTemplating -- it is unable to do so and fails. Ajax4JSF could fix both of these problems -- I cannot. Based on these stack traces, I would strongly suggest that you not include Ajax4JSF in a shared lib area as it will effect ALL JSF applications, not just the ones you want it to effect. Instead place the Ajax4JSF jar files in the WEB-INF/lib of your application(s)." -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/RF-1255?page=all ] Nick Belaevski resolved RF-1255. -------------------------------- Resolution: Out of Date -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira