David, The jarLocation null check in AppModule constructor is causing problems. The jarLocation can be passed as null when starting an embedded container. See ConfigurationFactory.configureApplication(ClassLoader, String, List<File>). I'm not really sure what value jarLocation should be set to in this case.
Jarek On Sat, Aug 21, 2010 at 12:58 PM, <[email protected]> wrote: > Author: dblevins > Date: Sat Aug 21 16:58:57 2010 > New Revision: 987790 > > URL: http://svn.apache.org/viewvc?rev=987790&view=rev > Log: > Better support for standalone modules > Partial revert of change allowing AppInfo.jarPath to be null -- this broke > the tomcat integration, deploy tool and a few other things. > Strict non-null check on App id/path throughout deployment. > Partial merge of David Jencks' code for a better > "openejb.strict.interface.declaration" mode. Still needs to be enabled and > related tests flushed out >
