From 1b1792aabec9c97c73feb80f282e6efb44112b4b Mon Sep 17 00:00:00 2001 From: Michael Bayne Date: Mon, 25 Oct 2010 20:16:40 +0000 Subject: [PATCH] Hah! Perhaps there was some use in having the class be named. However, I'm not sure what this is really testing. If the CRUD test with CustomType works, then transforming field marshallers work, so why do we need to make sure they have a specific class name? --- src/test/java/com/samskivert/depot/TransformTest.java | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/src/test/java/com/samskivert/depot/TransformTest.java b/src/test/java/com/samskivert/depot/TransformTest.java index d6c2ef0..8edbb10 100644 --- a/src/test/java/com/samskivert/depot/TransformTest.java +++ b/src/test/java/com/samskivert/depot/TransformTest.java @@ -193,8 +193,7 @@ public class TransformTest extends TestBase assertTrue(FieldMarshaller.createMarshaller(field) != null); field = TransformRecord.class.getField("custom"); - assertTrue(FieldMarshaller.createMarshaller(field).getClass(). - getName().endsWith("FieldMarshaller$TransformingMarshaller")); + assertTrue(FieldMarshaller.createMarshaller(field) != null); } // @Test public void testInvalidFieldAnnotation ()