You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Jeremy Hughes (JIRA)" <ji...@apache.org> on 2011/02/10 18:32:03 UTC
[jira] Updated: (ARIES-110) Equals methods for some Metadata
classes
[ https://issues.apache.org/jira/browse/ARIES-110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeremy Hughes updated ARIES-110:
--------------------------------
Affects Version/s: (was: 1.0)
0.1
0.2
0.3
Fix Version/s: (was: 1.0)
This isn't fixed, so removed the fix version
> Equals methods for some Metadata classes
> ----------------------------------------
>
> Key: ARIES-110
> URL: https://issues.apache.org/jira/browse/ARIES-110
> Project: Aries
> Issue Type: Bug
> Components: Blueprint
> Affects Versions: 0.1, 0.2, 0.3
> Reporter: David Jencks
> Attachments: ARIES-110.diff
>
>
> Dealing intelligently with MapMetadata in NamespaceHandlers would be a lot simpler if metadata for keys behaved more like the objects they represent. For my purposes in xbean-blueprint methods on
> RefMetadataImpl
> ValueMetadataImpl
> ServiceReferenceMetadataImpl
> ReferenceMetadataImpl
> seem reasonable. I'm not sure how to reasonably implement equals on other metadata types.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira