geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick McGuire (JIRA)" <>
Subject [jira] Closed: (GERONIMO-2245) Why corbaNameGroup:css-name?
Date Wed, 01 Nov 2006 19:29:17 GMT
     [ ]

Rick McGuire closed GERONIMO-2245.

    Fix Version/s: 1.2
                       (was: 1.1.x)
       Resolution: Fixed

I've not found any strong support for keeping this (or even any use of it).  Removed in 1.2

Committed revision 470046.

> Why corbaNameGroup:css-name?
> ----------------------------
>                 Key: GERONIMO-2245
>                 URL:
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: deployment, OpenEJB
>    Affects Versions: 1.1
>            Reporter: Aaron Mulder
>         Assigned To: Rick McGuire
>             Fix For: 1.2
> Between Geronimo 1.0 and Geronimo 1.1, we removed most of the elements that allow you
to list a full ObjectName/AbstractName in a reference.  There is no more "target-name" for
resource references, EJB references, etc.
> However, the corbaNameGroup still includes css-name, which appears to take the text of
an AbstractName or AbstractNameQuery to identify a CSS.  That seems weird, since there's already
the "css" element (type patternType) which lets you explicitly identify a CSS by its name
> I think we should remove css-name to be consistent (and avoid people trying to use the
AbstractName or AbstractNameQuery String syntax), unless there's a strong reason to keep it.

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