[
https://issues.jboss.org/browse/ISPN-7652?page=com.atlassian.jira.plugin....
]
Galder Zamarreño commented on ISPN-7652:
----------------------------------------
For reference: I was unable to replicate same issue in master. It turns out that the
"jboss-marshalling-osgi" package also contains the River classes. Even so, both
master and 8.2.x end up shipping River marshaller 1.4.10 jars in its own module. The fact
that master does not probably means that River marshaller 1.4.x module does not end up
getting imported by the Infinispan Hot Rod layer, whereas in 8.2.x it somehow does and
hence the River marshaller classes in "jboss-marshalling-osgi" module get mixed
up.
I didn't know but server/integration/bin directory contains some scripts to help with
module dependencies. After talking to [~NadirX], he's agreed to take over since
he's more knowledgeable on all this module business, because a question to ask is
whether the River marshaller module jar could be ignored or trimmed, but having had a
quick look to the module dependencies, seems like some Wildfly internals use it.
Incorrect River marshaller in server
------------------------------------
Key: ISPN-7652
URL:
https://issues.jboss.org/browse/ISPN-7652
Project: Infinispan
Issue Type: Task
Components: Marshalling, Server
Affects Versions: 8.2.6.Final, 9.0.0.CR3
Reporter: Galder Zamarreño
Assignee: Tristan Tarrant
Fix For: 9.0.0.CR4, 8.2.7.Final
After upgrading JBoss Marshalling to 2.0.0.Beta3, we forgot to apply similar changes to
force JBoss Marshaller's River to be in sync. As a result, the server currently ships
River 1.4.10 version which causes issues mentioned
[
here|https://github.com/infinispan/infinispan/pull/4709]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)