On May 14, 2013, at 3:34 PM, Mircea Markus <mmarkus(a)redhat.com> wrote:
On 14 May 2013, at 13:52, Galder Zamarreño wrote:
> Indeed, dunno what the environment this is working on, but indeed there's been
some crucial changes.
>
> Data container keyEquivalence configuration must be set to a Equivalence
implementation that can handle byte array keys. (If set, that same one will be used to
compare values too).
Isn't that set by default? I mean if you download the server you'd kind of expect
the client/server to work out of the box ;-)
^ Tristan's new server stuff should have that by default beucase the server provides a
default configuration which is configured correctly, hence why his server stuff works.
But, in the old server runnable stuff, you provided the configuration (or the default
configuration as defined by new ConfigurationBuilder().build() is used), so you need to
make sure it's rightly configured. Not sure which is downloadable right now...
Since it's the former we're moving towards, and trying to change the configuration
from the Hot Rod server had some issues (you don't get the builder, but get the
immutable configuration object, and as emailed to you when Tristan had issues with the
server, I didn't wanna make the configuration mutable just for this…), I didn't
make Hot Rod server force any configuration changes.
Cheers,
Cheers,
--
Mircea Markus
Infinispan lead (
www.infinispan.org)
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
--
Galder Zamarreño
galder(a)redhat.com
twitter.com/galderz
Project Lead, Escalante
http://escalante.io
Engineer, Infinispan
http://infinispan.org