I resolved it by following the Don't Do That pattern and not loading the datatype twice.
Event with hashCode and equals on the datatype it does not match as the datatype equality is checked with ==. I will find and document the issue here. But I am leaning toward the type registry issuing a warning when a datatype is registered a second time. Claude On Fri, Sep 28, 2018 at 9:45 AM Andy Seaborne <a...@apache.org> wrote: > Claude - > > Did you resolve this? > > In experimentation, I found a subtype of AdhocDatatype had to implement > .hashCode and .equals. > > Andy > -- I like: Like Like - The likeliest place on the web <http://like-like.xenei.com> LinkedIn: http://www.linkedin.com/in/claudewarren
