[infinispan-issues] [JBoss JIRA] Commented: (ISPN-1205) Redesign marshallers to be per named cache instance, per thread

[Galder Zamarreño (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-1205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12619075#comment-12619075 ] 

Galder Zamarreño commented on ISPN-1205:
----------------------------------------

A bit of restructuring of marshallers is needed here and hence it's not a trivial task. Basically, two types of marshallers are needed here: one global, one per cache. The global one is needed for JGroups marshaller, because when it gets JGroups message and it needs to unmarshall it, it has no clue which cache's marshaller to use and you can't just give any cache's marshaller to it. The per cache marshaller is the one that can be associated with a classloader via AdvancedCache.with() and the one that can marshalling for MarshalledValues...etc.

> 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