So, the Module contains TWO ValueSerialization systems, both the OrgJson and the Jackson ones.
That should then raise the question, Why don't we get AmbigiousTypeException?? There are also a MemoryEntityStore and a UuidIdentityGenerator in the Module.... Where are those coming from? Cheers On Fri, Jul 10, 2015 at 4:25 PM, Niclas Hedhman <[email protected]> wrote: > > I think I have found a Testcase problem, while trying to improve the > ValueSerialization subsystem. > > To show what I mean; > > a. Put a breakpoint on the first line in the only(!) test in > AbstractValueCompositeSerializationTest > > b. Run the JacksonValueCompositeSerializationTest. > > c. At breakpoint, look at the this.valueSerialization member. It has a > ServiceComposite reference to the OrgJsonValueSerializationService, not > the Jackson one. > > > I am trying to figure out how this is at all possible. > > > Cheers > -- > Niclas Hedhman, Software Developer > http://zest.apache.org - New Energy for Java > -- Niclas Hedhman, Software Developer http://zest.apache.org - New Energy for Java
