There are lots of places in Joda-Time where we rely on == rather than .equals(). This patch certainly won't be sufficient to fix all those places.
In order to change Joda-Time to solve an issue like this I would need proof (eg. someone from Terracotta) saying that this cannot be fixed by a change in the Terracotta setup. Basically, comparing objects using == is a fundamental Java concept, and a tool like Terracotta really needs to support it. Stephen On 26/03/2008, Johannes Schneider <[EMAIL PROTECTED]> wrote: > Okay, > > I have created a small patch that seems to fix my problems. It can be > downloaded at > http://cedarsoft.de/tmp/terracotta_compatibility_patch.patch > > I am not sure whether that is enough for terracotta support, but for me > it works so far. > And I don't understand whether I have added a pitfall to Joda time. > > The problem is that > org.joda.time.base.AbstractPartial#compareTo > compares the field types using "!=" but when using a cluster those > instances are not identical. > So I have added a simple "equals" method to > org.joda.time.DateTimeFieldType.StandardDateTimeFieldType. > > > At the moment I use that patched version successfully. It would be great > if anyone could take a look at that patch and give some comments whether > that is a valid change that could be added to the trunk. ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Joda-interest mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/joda-interest
