geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Mulder (JIRA)" <...@geronimo.apache.org>
Subject [jira] Created: (GERONIMO-2245) Why corbaNameGroup:css-name?
Date Sat, 29 Jul 2006 23:12:14 GMT
Why corbaNameGroup:css-name?
----------------------------

                 Key: GERONIMO-2245
                 URL: http://issues.apache.org/jira/browse/GERONIMO-2245
             Project: Geronimo
          Issue Type: Bug
      Security Level: public (Regular issues)
          Components: deployment, OpenEJB
    Affects Versions: 1.1
            Reporter: Aaron Mulder
             Fix For: 1.1.x


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
components.

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: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message