[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [sca-j] NEW ISSUE: equals() method on ServiceReference and CallableReference
If the equals method involves comparing URIs for equality, do we need to say some words about how URIs should be compared? I can provide some words if needed. All the best, Ashok Mark Combellack wrote: > > RAISER: Mark Combellack > > TARGET: SCA Java Common Annotations and APIs > > DESCRIPTION: > > The equals() and hashCode() methods are some of the fundamental Java > Object methods that are used for comparing objects. The SCA Java > specifications do not describe what should happen when the equals() or > hashCode() methods are called on a ServiceReference or CallableReference. > > Without an explicit statement, SCA developers will not know whether > they can compare ServiceReferences and CallableReferences. > > I’ve sent an email to the SCA-Java list (see link below) that contains > an example usage scenario. > > http://lists.oasis-open.org/archives/sca-j/200805/msg00037.html > > > PROPOSAL: > > Update the specification to state that the equals() method for > ServiceReference can be used to test whether they refer to the same > target. > > Update the specification to state that the equals() method for > CallableReference can be used to test whether they refer to the same > target. > > Update the specification to state that the hashCode() method for > ServiceReference and CallableReference must comply with the hashCode() > contract as defined by Java - see > http://java.sun.com/j2se/1.5.0/docs/api/java/lang/Object.html#hashCode() > <http://java.sun.com/j2se/1.5.0/docs/api/java/lang/Object.html#hashCode%28%29> > > > Mark Combellack| Software Developer| Avaya | Eastern Business Park | > St. Mellons | Cardiff | CF3 5EA | Voice: +44 (0) 29 2081 7624 | > mcombellack@avaya.com <mailto:%7Cmcombellack@avaya.com> >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]