Paul, I¹m trying to track down this LocalCache problem that was introduced on commit r1290973. What I¹ve noticed is that it fails when it thinks two methods have the same signature. For example I see this list of methods:
[ public static org.oclc.platform.opensocial.spi.ApplicationId org.oclc.platform.opensocial.spi.ApplicationId.valueOf(java.lang.String), public java.lang.Long org.oclc.platform.opensocial.spi.ApplicationId.getValue(), public java.io.Serializable org.oclc.platform.opensocial.spi.ApplicationId.getValue(),public boolean org.oclc.platform.opensocial.spi.ObjectId.equals(java.lang.Object), public java.lang.String org.oclc.platform.opensocial.spi.ObjectId.toString(), public int org.oclc.platform.opensocial.spi.ObjectId.hashCode(), public final void java.lang.Object.wait() throws java.lang.InterruptedException, public final native void java.lang.Object.wait(long) throws java.lang.InterruptedException, public final void java.lang.Object.wait(long,int) throws java.lang.InterruptedException, public final native java.lang.Class java.lang.Object.getClass(), public final native void java.lang.Object.notify(), public final native void java.lang.Object.notifyAll() ] When JsonUtil¹s LoadingCache processes it it end up with a of methods like this [ value=public java.lang.Long org.oclc.platform.opensocial.spi.ApplicationId.getValue(), value=public java.io.Serializable org.oclc.platform.opensocial.spi.ApplicationId.getValue() ] When methods.build() is called it blows up with java.lang.IllegalArgumentException: duplicate key: value If I rollback JsonUtil to the version before this commit I no longer have the issue. Ideas? doug On 3/5/12 5:33 PM, "daviesd" <davi...@oclc.org> wrote: > I just got back from vacation and pulled down today¹s 2.5.0. Some of my unit > tests that derive from AbstractLargeRestfulTests are failing deep in the > bowels of LocalCache.java. Specifically I get a > > java.util.concurrent.ExecutionException: java.lang.IllegalArgumentException: > duplicate key: value > > exception when recordMisses is being called. I know there was a recent > upgrade to guava 11.0.1. Wondering if this might be affecting this. Does > this make sense to anyone? If so, let me know. > > Doug
