You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "David Jencks (JIRA)" <ji...@apache.org> on 2010/01/10 18:53:54 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 ]
David Jencks updated ARIES-110:
-------------------------------
Attachment: ARIES-110.diff
implementation of equals/hashcode for a few Metadata objects.
> 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: 1.0
> Reporter: David Jencks
> Fix For: 1.0
>
> 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.
-
You can reply to this email to add a comment to the issue online.