Hey Gavin, we was able to figure out the class loader issue. Basically, we had copied the faces libraries (myfaces-api-1.1.4.jar. myfaces-impl-1.1.4.jar) to the jboss server (in the tomcat jsflibs directory) and we did not include them in our ear.
When we copied them back to the ear level and included them there, the problem went away. I bet the class loader at the jboss level was the one loading the faces stuff and it did not have visibility into the application classes and thus it threw this exception. >From your point of view, what is the best practice and why do you think this >error happened? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3979723#3979723 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3979723 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
