[infinispan-issues] [JBoss JIRA] Issue Comment Edited: (ISPN-1205) Redesign marshallers to be per named cache instance, per thread
[
https://issues.jboss.org/browse/ISPN-1205?page=com.atlassian.jira.plugin....
]
Galder Zamarreño edited comment on ISPN-1205 at 7/25/11 1:12 PM:
-----------------------------------------------------------------
Correction:
Some important considerations:
- Transport (global component), requires a marshaller to be set on the given
RpcDispatcher. It's not clear when this needs doing, but could deferred to a cache
component startup (i.e. RpcManager) rather than rely on the global component startup (i.e.
Transport)
was (Author: galder.zamarreno):
Some important considerations:
- Transport (global component), requires a marshaller to be set on startup (JGroups
mandates this) as part of the RpcDispatcher initialization.
Redesign marshallers to be per named cache instance, per thread
---------------------------------------------------------------
Key: ISPN-1205
URL: https://issues.jboss.org/browse/ISPN-1205
Project: Infinispan
Issue Type: Feature Request
Affects Versions: 5.0.0.CR6
Reporter: Pete Muir
Assignee: Galder Zamarreño
Fix For: 5.1.0.BETA1
Since we have switched to explicit classloaders in Infinispan 5.0, we can now pass the
correct classloader to use into JBoss Marshalling, rather than rely on the TCCL. However
at the moment marshallers are per thread, not per named cache instance. We will need to
change the way marshallers are created to make a marshaller
per-thread-per-named-cache-instance. This will also require investigation of the best way
of propagating this through the DI system. Dan has previously suggested using the
InvocationContext
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira