On Sep 15, 2006, at 10:35 AM, ant elder wrote:
It looks like extensions don't work in webapps because LauncherImpl
getInstallDirectory is returning a bad File. The URL obtained for the
LauncherImpl class is:
jar:jndi:/localhost/scriptWebapp/WEB-INF/tuscany/boot/core-
1.0-incubator-M2-SNAPSHOT.jar!/org/apache/tuscany/core/launcher/
LauncherImpl.class
so the FIle that ends up being returned is:
jndi:\localhost\scriptWebapp\WEB-INF\tuscany
so later in DirectoryScanExtender init the test for if the
extensionDir.isDirectory returns false.
An ideas what the correct thing for getInstallDirectory to be doing?
It probably should not be called at all (as there is no install
directory in a webapp) and we really should not have the
DirectoryScanExtender in the webapp configuration either as there is
no guarantee there will be a physical filesystem underneath.
Perhaps the best thing here is not to have the servlet code use the
command line launcher (which is what LauncherImpl is). We should be
able to separate out things that are generic to bootstrap (like
loading the system and application composites given their scdl), but
things like install directory etc. should be separate.
I started to move some things around before getting buried in build
work e.g. having the listener figure handle parsing the init param
and then just setting the locations via the WebappRuntime interface.
I was trying to make the impl one that could just be configured as I
thought it would be easier to share bits between them.
--
Jeremy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
