[ http://issues.apache.org/jira/browse/MYFACES-594?page=comments#action_12330268 ]
Jamie Cash commented on MYFACES-594: ------------------------------------ The RC1 test was a red herring, the problem was caused by a bug in all recent JBoss versions (I will raise with JBoss shortly) where a deployed application will sometimes use classes from a jar file contained within another deployed application instead of its own jar files. For example, app1 is deployed with myfaces-all nightly build version and app2 is deployed with with myfaces-all release version. It is possible that app1 will use classes from myfaces-all release version instead of myfaces-all nightly build version. In the case that caused this issue to be raised, I had deployed an application that used Oracle ADF faces as well as the application that I was testing. The application that I was testing used JSF classes from the oracle ADF libraries that was deployed in the other application, and complained that it wasn't configured. I will raise this issue with JBoss. It is safe to close this myfaces issue now. > Examples and myfaces 1.0.9 apps don't work on tomcat 5.5 running under JBoss > ---------------------------------------------------------------------------- > > Key: MYFACES-594 > URL: http://issues.apache.org/jira/browse/MYFACES-594 > Project: MyFaces > Type: Bug > Components: General > Versions: 1.1.0, Nightly Build > Environment: Tomcat 5.5 running under JBoss on a windows 2003 server > Reporter: Jamie Cash > Priority: Blocker > > None of the examples from the nightly build and 1.1.0 run when deployed on > JBoss on a windows 2003 server. The first page is blank and the following > warning is logged: > 2005-09-21 10:17:13,662 INFO [STDOUT] 21-Sep-2005 10:17:13 > oracle.adfinternal.view.faces.webapp.AdfFacesFilterImpl > verifyFilterIsInstalled > WARNING: The AdfFacesFilter has not been installed. ADF Faces requires this > filter for proper execution. > This also affects all of the applications that we developed under myfaces > 1.0.9. It is possible to get these to work inconsistantly though by adding > the jsf-impl.jar to the deployment, but this only works sometimes, depending > on whether myfaces-all.jar or jsf-impl.jar is the first on the classpath. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
