[
https://issues.jboss.org/browse/ISPN-1206?page=com.atlassian.jira.plugin....
]
Galder Zamarreño commented on ISPN-1206:
----------------------------------------
Reopening this cos it's not a good idea to change the default cache in EDG but leave
it as it is in the Infinispan REST server. As noted in
https://issues.jboss.org/browse/JBPAPP-6777?focusedCommentId=12618719&...
- we can't just change the default cache name in REST because there's an implicit
link between the current default cache name and the associated configuration (even though
it's not documented), and that's been there since day one. So, changing REST's
default cache would effectively break the REST protocol.
So, as proposed in that comment, we could change the default cache name for the Memcached
server because there're no links between the protocol and the cache that's used
underneath. To maintain same logic, the new Memcached default cache would just need to
clone the default cache configuration. That'd be very simple to implement.
rest and memcached server modules aren't isolated and affect each
other
-----------------------------------------------------------------------
Key: ISPN-1206
URL:
https://issues.jboss.org/browse/ISPN-1206
Project: Infinispan
Issue Type: Bug
Components: Cache Server
Affects Versions: 5.0.0.CR4
Reporter: Michal Linhard
Assignee: Galder Zamarreño
if we work with the same key with REST and memcached client at once, a server side class
cast exception occurs because both work with different value representation:
SERVER_ERROR java.lang.ClassCastException: [B cannot be cast to
org.infinispan.server.memcached.MemcachedValue
SERVER_ERROR java.lang.ClassCastException: [B cannot be cast to
org.infinispan.server.core.CacheValue
this happens when both server modules use shared cache manager
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira