You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "David Jencks (JIRA)" <de...@geronimo.apache.org> on 2006/09/16 00:37:25 UTC
[jira] Created: (GERONIMO-2409) Provide config/module aliasing
ability
Provide config/module aliasing ability
--------------------------------------
Key: GERONIMO-2409
URL: http://issues.apache.org/jira/browse/GERONIMO-2409
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
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: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-2409) Provide config/module aliasing
ability
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2409?page=comments#action_12447899 ]
David Jencks commented on GERONIMO-2409:
----------------------------------------
rev 472213 added a client_artifact_aliases.properties file in boilerplate-j2ee so the client can swap stuff too.
> Provide config/module aliasing ability
> --------------------------------------
>
> Key: GERONIMO-2409
> URL: http://issues.apache.org/jira/browse/GERONIMO-2409
> 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: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-2409) Provide config/module aliasing
ability
Posted by "Rick McGuire (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2409?page=comments#action_12437612 ]
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: http://issues.apache.org/jira/browse/GERONIMO-2409
> 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: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-2409) Provide config/module aliasing
ability
Posted by "David Jencks (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2409?page=comments#action_12435942 ]
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: http://issues.apache.org/jira/browse/GERONIMO-2409
> 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: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-2409) Provide config/module aliasing
ability
Posted by "Joe Bohn (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2409?page=comments#action_12435490 ]
Joe Bohn commented on GERONIMO-2409:
------------------------------------
Not sure if voting still matters ... but here's my +1
> Provide config/module aliasing ability
> --------------------------------------
>
> Key: GERONIMO-2409
> URL: http://issues.apache.org/jira/browse/GERONIMO-2409
> 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: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-2409) Provide config/module aliasing
ability
Posted by "David Jencks (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2409?page=all ]
David Jencks updated GERONIMO-2409:
-----------------------------------
Attachment: GERONIMO-2409-v1.patch
Change the explicit version resolution to do module aliasing as well. This removes the ability to have a version for an entire groupId. I originally included this only because I was too lazy to write up an entire explicit_versions.properties for the entire server. Since Jason has made the car plugin automatically generate a complete explicit_versions file for each car, I think removing this functionality is a step forward.
> Provide config/module aliasing ability
> --------------------------------------
>
> Key: GERONIMO-2409
> URL: http://issues.apache.org/jira/browse/GERONIMO-2409
> 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: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-2409) Provide config/module aliasing
ability
Posted by "Jeff Genender (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2409?page=comments#action_12435495 ]
Jeff Genender commented on GERONIMO-2409:
-----------------------------------------
+1...looks good to me
> Provide config/module aliasing ability
> --------------------------------------
>
> Key: GERONIMO-2409
> URL: http://issues.apache.org/jira/browse/GERONIMO-2409
> 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: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira