geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <>
Subject [jira] Assigned: (GERONIMO-3140) Artifact aliasing doesn't work for already-started modules
Date Mon, 30 Jul 2007 21:36:52 GMT


David Jencks reassigned GERONIMO-3140:

    Assignee: David Jencks

> Artifact aliasing doesn't work for already-started modules
> ----------------------------------------------------------
>                 Key: GERONIMO-3140
>                 URL:
>             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.

View raw message