I had a similar problem recently (http://openejb.979440.n4.nabble.com/Can-you-configure-tomee-to-not-scan-a-jar-in-WEB-INF-lib-td4649006.html) caused by tomee scanning a jar file i had in my WEB-INF/lib. Fortunately for me, the offending jar file didn't contain any managed beans, so i was able to configure tomee to exclude that jar from scanning at startup which resolved my issue.
-- View this message in context: http://openejb.979440.n4.nabble.com/richfaces-4-2-2-deploy-problem-tp4655415p4655441.html Sent from the OpenEJB User mailing list archive at Nabble.com.
