On Aug 23, 2010, at 2:17 PM, Jarek Gawor wrote: > Committed a small fix in revision 988313 that seems to work for me. > Let me know if that seems ok to you too. >
That's good enough for now. Tweaked it a bit more so that not supplying APP_NAME results in the module being counted as a standalone module which affects the global jndi names generated. -David > On Mon, Aug 23, 2010 at 2:36 PM, Jarek Gawor <[email protected]> wrote: >> 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 >>> >> >
