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)" <ji...@apache.org> on 2007/05/04 22:01:15 UTC
[jira] Created: (GERONIMO-3140) Artifact aliasing doesn't work for
already-started modules
Artifact aliasing doesn't work for already-started modules
----------------------------------------------------------
Key: GERONIMO-3140
URL: https://issues.apache.org/jira/browse/GERONIMO-3140
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Components: deployment
Affects Versions: 2.0-M5
Reporter: David Jencks
Fix For: Wish List
We normally alias server modules on the client so that a reference to e.g. the transaction-jta11 module gets turned into a reference to client-transaction. However if the module with this reference is already started on the server while deployment is happening, there's no opportunity to do this aliasing during deployment. E.g. the openjpa module depends on the tm module and is normally started: so any app client using opnejpa will appear at deploy time to have 2 tms, one from tx-jta11 through the openjpa dependency and one from client-transaction.
One hacky workaround is to ignore duplicate gbean matches during deployment.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-3140) Artifact aliasing doesn't work for
already-started modules
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Jencks closed GERONIMO-3140.
----------------------------------
Resolution: Fixed
Fix Version/s: (was: Wish List)
2.1
I think the last bunch of changes fixed this problem.
> Artifact aliasing doesn't work for already-started modules
> ----------------------------------------------------------
>
> Key: GERONIMO-3140
> URL: https://issues.apache.org/jira/browse/GERONIMO-3140
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: deployment
> Affects Versions: 2.0-M5
> Reporter: David Jencks
> Assignee: David Jencks
> Fix For: 2.1
>
>
> We normally alias server modules on the client so that a reference to e.g. the transaction-jta11 module gets turned into a reference to client-transaction. However if the module with this reference is already started on the server while deployment is happening, there's no opportunity to do this aliasing during deployment. E.g. the openjpa module depends on the tm module and is normally started: so any app client using opnejpa will appear at deploy time to have 2 tms, one from tx-jta11 through the openjpa dependency and one from client-transaction.
> One hacky workaround is to ignore duplicate gbean matches during deployment.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3140) Artifact aliasing doesn't work
for already-started modules
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12516659 ]
David Jencks commented on GERONIMO-3140:
----------------------------------------
These changes may help the situation:
trunk rev 561259
2.0 rev 561286
daytrader (schema mods) rev 561287.
Use PatternType element for external rars, and external paths, and cook up an ArtifactResolver so you can leave bits out. This means client_artifact_aliases.properties will be used when available to help with app client deployment.
> Artifact aliasing doesn't work for already-started modules
> ----------------------------------------------------------
>
> Key: GERONIMO-3140
> URL: https://issues.apache.org/jira/browse/GERONIMO-3140
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: deployment
> Affects Versions: 2.0-M5
> Reporter: David Jencks
> Assignee: David Jencks
> Fix For: Wish List
>
>
> We normally alias server modules on the client so that a reference to e.g. the transaction-jta11 module gets turned into a reference to client-transaction. However if the module with this reference is already started on the server while deployment is happening, there's no opportunity to do this aliasing during deployment. E.g. the openjpa module depends on the tm module and is normally started: so any app client using opnejpa will appear at deploy time to have 2 tms, one from tx-jta11 through the openjpa dependency and one from client-transaction.
> One hacky workaround is to ignore duplicate gbean matches during deployment.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-3140) Artifact aliasing doesn't work for
already-started modules
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Jencks reassigned GERONIMO-3140:
--------------------------------------
Assignee: David Jencks
> Artifact aliasing doesn't work for already-started modules
> ----------------------------------------------------------
>
> Key: GERONIMO-3140
> URL: https://issues.apache.org/jira/browse/GERONIMO-3140
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: deployment
> Affects Versions: 2.0-M5
> Reporter: David Jencks
> Assignee: David Jencks
> Fix For: Wish List
>
>
> We normally alias server modules on the client so that a reference to e.g. the transaction-jta11 module gets turned into a reference to client-transaction. However if the module with this reference is already started on the server while deployment is happening, there's no opportunity to do this aliasing during deployment. E.g. the openjpa module depends on the tm module and is normally started: so any app client using opnejpa will appear at deploy time to have 2 tms, one from tx-jta11 through the openjpa dependency and one from client-transaction.
> One hacky workaround is to ignore duplicate gbean matches during deployment.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3140) Artifact aliasing doesn't work
for already-started modules
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493786 ]
David Jencks commented on GERONIMO-3140:
----------------------------------------
Workaround committed in rev 535367
> Artifact aliasing doesn't work for already-started modules
> ----------------------------------------------------------
>
> Key: GERONIMO-3140
> URL: https://issues.apache.org/jira/browse/GERONIMO-3140
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: deployment
> Affects Versions: 2.0-M5
> Reporter: David Jencks
> Fix For: Wish List
>
>
> We normally alias server modules on the client so that a reference to e.g. the transaction-jta11 module gets turned into a reference to client-transaction. However if the module with this reference is already started on the server while deployment is happening, there's no opportunity to do this aliasing during deployment. E.g. the openjpa module depends on the tm module and is normally started: so any app client using opnejpa will appear at deploy time to have 2 tms, one from tx-jta11 through the openjpa dependency and one from client-transaction.
> One hacky workaround is to ignore duplicate gbean matches during deployment.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.