[infinispan-dev] Data Container configuration changes

[Tristan Tarrant]

On 27/10/16 16:01, William Burns wrote:
> Not sure I understand, so you are saying to remove it from the
> parser/xsd but keep it in the programmatic configuration?  And just to
> clarify the new binary element would replace storeAsBinary.

Yes. The parser, when confronted with a pre 9.0 schema, would print out 
a warning, but it would use the new binary element internally.

> Equivalence is only used when you are storing byte[] objects, which
> Infinispan would support directly with no configuration with the new
> changes (we would wrap the byte[] to ensure equals/hashCode).
> Compatibility would work the same way it does right now, I just had to
> add in some handling for the wrapper in some parts of code.

Great. Go ahead.

Tristan


-- 
Tristan Tarrant
Infinispan Lead
JBoss, a division of Red Hat