geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <>
Subject [jira] Commented: (GERONIMO-2409) Provide config/module aliasing ability
Date Tue, 19 Sep 2006 17:31:23 GMT
    [ ] 
David Jencks commented on GERONIMO-2409:

I've committed in rev 447920 enough to get my experimental jee5 servers to start, by changing
only the artifact resolution code.  I don't really see why it works yet: I expected we'd need
similar code in Configuration and Kernel gbean lookup methods.  I'm leaving this open until
we find out if more work is needed.

> 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