[
https://issues.redhat.com/browse/ISPN-11974?page=com.atlassian.jira.plugi...
]
Dan Berindei updated ISPN-11974:
--------------------------------
Description: Currently if the {{infinispan-jboss-marshalling}} module is on the client
classpath we automatically configure the client marshaller to be
{{GenericJBossMarshaller}}. This causes issues with our testsuite, as the module is often
on the classpath. Furthermore, we want users to start transitioning away from JBoss
Marshalling. Therefore, from Infinispan -12- 11 we should no automatically configure this
marshaller if the module is present. (was: Currently if the
{{infinispan-jboss-marshalling}} module is on the client classpath we automatically
configure the client marshaller to be {{GenericJBossMarshaller}}. This causes issues with
our testsuite, as the module is often on the classpath. Furthermore, we want users to
start transitioning away from JBoss Marshalling. Therefore, from Infinispan 12 we should
no automatically configure this marshaller if the module is present.)
Remove GenericJbossMarshaller automatic configuration
-----------------------------------------------------
Key: ISPN-11974
URL:
https://issues.redhat.com/browse/ISPN-11974
Project: Infinispan
Issue Type: Task
Components: Configuration, Hot Rod
Affects Versions: 11.0.0.CR1
Reporter: Ryan Emerson
Assignee: Ryan Emerson
Priority: Major
Fix For: 11.0.0.Final
Currently if the {{infinispan-jboss-marshalling}} module is on the client classpath we
automatically configure the client marshaller to be {{GenericJBossMarshaller}}. This
causes issues with our testsuite, as the module is often on the classpath. Furthermore, we
want users to start transitioning away from JBoss Marshalling. Therefore, from Infinispan
-12- 11 we should no automatically configure this marshaller if the module is present.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)