You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Rick McGuire (JIRA)" <ji...@apache.org> on 2006/11/01 20:29:17 UTC
[jira] Closed: (GERONIMO-2245) Why corbaNameGroup:css-name?
[ http://issues.apache.org/jira/browse/GERONIMO-2245?page=all ]
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: 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
> 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 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