This is a version of ConcreteElement that sotores object in the Map only if you give explicitly a key-name, otherwise it stores only in the Vector.
That seems to work good, with a good retro-compatibility.
I modified classes since the jakarta ECS SVN repository.
You will find the ConcreteElement class, and subsequent 5 classes adaptions.
Pay attention, these patches are based on the trunk, not the 1.4.2 version.
> addElement(Element element) methods can fail
> Key: ECS-1
> URL: https://issues.apache.org/jira/browse/ECS-1 > Project: ECS
> Issue Type: Bug
> Environment: in Ibm Virtual Machines, but probabily also in Sun Virtual Machines
> Reporter: Mauro Manfrin
> Priority: Critical
> Attachments: ecs-maintrunk-patches.zip
> The class ConcreteElement exposes a method
> addElement(Element element)
> that calls
> so it gives a key valued element.hashCode() to that element.
> That's the point: element.hashCode() can't be a unique key because sometimes we can have two elements with the same hasocode.
> javadoc states:
> "It is not required that if two objects are unequal according to the
> equals(java.lang.Object) method, then calling the hashCode method on each of
> the two objects must produce distinct integer results. However, the
> programmer should be aware that producing distinct integer results for
> unequal objects may improve the performance of hashtables."
> So sometimes, two different objects can have the same hashCode!
> So, sometimes two calls to addElement(element) can result in only the second
> object stored in the ConcreteElement.
> So sometimes, on out instalaltion some table rows misses, or some row cells
> misses or...
This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.