After talking to Ales and Scott on the JBAS5 call today I think you are right Pete that this is a new problem unrelated to jboss-seam-jbas5.jar. Scott can elaborate but this looks to be a problem related to how we scan for annotations, because there are classes in the jboss-seam-2.0.1.GA.jar that have member variables whose types are from jbpm, drools etc, e.g. org\jboss\seam\pageflow\Pageflow.java has a member variable of type org/jbpm/graph/exe/ProcessInstance. One question which came up was why we're not seeing this issue with other JEE 5 containers, which presumably also scan all deployments for annotations? PS adding all the extra jars to the deployment gets the app deploying fine. Its just extra baggage you shouldn't need. Cheers View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4125692#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...