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/07/31 02:43:52 UTC

[jira] Commented: (GERONIMO-2244) Explicit reference fail when module type is not "car"

    [ https://issues.apache.org/jira/browse/GERONIMO-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12516585 ] 

David Jencks commented on GERONIMO-2244:
----------------------------------------

No further work in the last year, and the actual problem was fixed.

> Explicit reference fail when module type is not "car"
> -----------------------------------------------------
>
>                 Key: GERONIMO-2244
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-2244
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: console, deployment
>    Affects Versions: 1.1
>            Reporter: Aaron Mulder
>             Fix For: 1.1.x
>
>
> Currently the <pattern> used in the naming schema includes group, artifact, and version, but not type.  In ENCConfigBuilder.buildAbstractNameQuery, the type is hardcoded to "car".  This means that if you use a naming:pattern with an artifactId, it only works if the target module's type is actually "car".  This is not true, for example, for several module types created by the admin console, as well as in general for user-defined modules.
> The naming:pattern element should include a "type" element, and ENCConfigBuilder (and any other necessary code) should respect it.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.