geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick McGuire (JIRA)" <>
Subject [jira] Commented: (GERONIMO-2409) Provide config/module aliasing ability
Date Mon, 25 Sep 2006 17:15:50 GMT
    [ ] 
Rick McGuire commented on GERONIMO-2409:

It would be nice if this aliasing carried through to at least deploy start/stop.  This would
be very handy for applications where they have a dependency on a system module where there
might be multiple choices (e.g., j2ee-corba, where there's a Sun ORB option or a Yoko ORB
option).  The artifact_aliases entry can identify the default by mapping j2ee-corba to one
of the options, and the system administrator need only worry about starting/stopping the j2ee-corba
module without needing to know which option was selected for use. 

> Provide config/module aliasing ability
> --------------------------------------
>                 Key: GERONIMO-2409
>                 URL:
>             Project: Geronimo
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: core
>    Affects Versions: 1.2
>            Reporter: David Jencks
>         Assigned To: David Jencks
>             Fix For: 1.2
>         Attachments: GERONIMO-2409-v1.patch
> It's sort of impossible to swap a basic configuration such as transaction with a substitute
such as transaction-jta11: there are too many modules that depend on it that all have to be
rebuilt just because you changed one name.
> To fix this we need some way to substitute one module (configuration) for another.  We
might aim for a function-based registry rather than a name based one, but that is more that
I want to think about right now.
> I've done some simple experiments and it looks like some trivial changes in DefaultArtifactResolver,
the car maven plugin, and an additional properties file in the server at least let you swap
modules and get the server started.  I expected that changes in the kernel gbean lookups and
Configuration gbean lookups would be necessary as well, but I haven't needed them yet.
> I think the changes so far should be applied since they clarify the explicit version
resolution code and enable at least some module swapping.  I suspect we'll find out soon if
more work is needed.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message