I had to temporarily gut our webapp scanning enhancements (include/exclude). Bottom line is that a WebModule can have at most one EjbModule (itself). The spec Collapsed EAR approach ended up being slightly different than our own. We can put all that back, but just to get things moving I gutted the extra features and boiled it down to the minimum.
When we put back the scanning include/export enhancements, we need to do it differently than we had before: 2011-02-15 19:35:30,199 - WARN - ADJUST THE EXCLUDE/INCLUDE!!!. Current settings: openejb.deployments.classpath.exclude='', openejb.deployments.classpath.include='' 2011-02-15 19:35:32,383 - INFO - Searched 63 classpath urls in 2184 milliseconds. Average 34 milliseconds per url. 2011-02-15 19:35:32,530 - INFO - Configuring enterprise application: /tmp/apache-tomcat-7.0.8/webapps/examples Only the WEB-INF/lib/*.jar files and WEB-INF/classes/ parts of the webapp classpath are eligible for scanning. So for this particular app that'd be these jars: /tmp/apache-tomcat-7.0.8/webapps/examples/WEB-INF/lib/jstl.jar /tmp/apache-tomcat-7.0.8/webapps/examples/WEB-INF/lib/standard.jar We were also adding the persistence units twice which resulted in any apps that referenced a unit by name to fail. -David
