]
Erik Salter commented on ISPN-2282:
-----------------------------------
Update -- after talking with the ISPN team, this is due to user externalizers now needing
to implement Serializable. Since this does put an onus on the users to update their code,
regression test, etc., can org.infinispan.marshall.Externalizer extends Serializable like
it was in 5.1?
Custom Externalizers cause NotSerializableException
---------------------------------------------------
Key: ISPN-2282
URL:
https://issues.jboss.org/browse/ISPN-2282
Project: Infinispan
Issue Type: Bug
Components: Core API
Affects Versions: 5.2.0.Alpha3
Reporter: Erik Salter
Assignee: Mircea Markus
Since org.infinispan.marshall.Externalizer no longer extends Serializable, my custom
Externalizers throw NotSerialazbleExceptions.
Example:
Caused by: org.infinispan.marshall.NotSerializableException:
net.beaumaris.odrm.resmanagement.type.ODRMSessionData$ODRMSessionDataExternalizer
Caused by: an exception which occurred:
in field externalizer
in object org.infinispan.marshall.jboss.JBossExternalizerAdapter@2c370555
-> toString =
org.infinispan.marshall.jboss.JBossExternalizerAdapter@2c370555
in object net.beaumaris.odrm.resmanagement.type.ODRMSessionData@62c91115
-> toString = ODRMSessionData [sopId=999991, segmentIndex=0,
streamerId=99999]
in object org.infinispan.commands.write.PutKeyValueCommand@cf4d21f7
-> toString =
PutKeyValueCommand{key=9d3d0a41-4d2a-4320-aa38-64a5203c49bf, value=ODRMSessionData
[sopId=999991, segmentIndex=0, streamerId=99999], flags=[SKIP_REMOTE_LOOKUP],
putIfAbsent=false, lifespanMillis=-1, maxIdleTimeMillis=-1}
in object org.infinispan.commands.remote.SingleRpcCommand@280f4ad0
-> toString = SingleRpcCommand{cacheName='ODRM_SESSION',
command=PutKeyValueCommand{key=9d3d0a41-4d2a-4320-aa38-64a5203c49bf, value=ODRMSessionData
[sopId=999991, segmentIndex=0, streamerId=99999], flags=[SKIP_REMOTE_LOOKUP],
putIfAbsent=false, lifespanMillis=-1, maxIdleTimeMillis=-1}}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: