On 01/10/18 07:52, Claude Warren wrote:
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.
Good - my cursory look at the code showed only use of Objects.equals.
But I am leaning toward the type registry issuing a warning when a
datatype is registered a second time.
As long as parsing unknown datatypes isn't impacted.
Andy
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
