Hi, this is the content of the email that I sent with the title jsr88
- ModuleConfigurer - still some classpath problems.
The online deployer, e.g. deployer.jar, needs to have geronimo-deploy-
config along with all the modules providing an implementation of this
interface added as MANIFEST ClassPath entries. It seems to me that to
have the relevant geonimo-*-builder is not so great: builders are
executed server side and actually install something on the server. It
seems to me that ModuleConfigurers are intended to be used
disconnected from the server during the configuration stage of
modules. So, perhaps that ModuleConfigurers should be move to their
own module in order to make that a little bit clearer. As you are
working on this David J., I would like to know if this makes sense or
if you have a better idea.
Thanks,
Gianny
On 09/01/2007, at 3:00 PM, David Jencks wrote:
On Jan 8, 2007, at 8:21 PM, [EMAIL PROTECTED] wrote:
Author: kevan
Date: Mon Jan 8 17:21:35 2007
New Revision: 494291
URL: http://svn.apache.org/viewvc?view=rev&rev=494291
Log:
Fix some deploy problems. geronimo-deploy-config needs to be in lib.
What goes wrong if it isn't? I wondered if this would be a problem.
New Configurers needed to be serializable...
what happens if they aren't? If we can't get away from this we
should make ModuleConfigurer extend Serializable...
I don't like adding more and more to lib..... if this is only
needed for jsr88 stuff I think we should consider starting up
something on request to load the configurer gbeas and register
them, using the repo.
thanks
david jencks
