Re: [infinispan-dev] Auto-detection of appropriate key2StringMapperClass
Every store can have its own Key2StringMapper, so I really don't think
service discovery is appropriate here.
My favourite solution would be to have a default Key2StringMapper
implementation that uses Java serialization (not our internal
marshalling, because that can change between versions). It could even
do base64 encoding for databases that don't have a VARBINARY/BYTEA
equivalent.
Cheers
Dan
On Wed, Mar 8, 2017 at 6:34 PM, Sanne Grinovero <sanne(a)infinispan.org> wrote:
It seems I keep forgetting that the "key2StringMapperClass"
needs to
be explicitly set when using the String based JDBC CacheStore, which I
think is a quite popular store.
http://infinispan.org/docs/dev/user_guide/user_guide.html#storing_the_ind...
I think we could remove the need to configure this with an appropriate
service discovery?
We could keep the property so to be able to override the discovery process.
Would anyone volunteer to implement this?
Thanks,
Sanne
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev