[jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1287) CacheLoader load operations cannot deserialize types not visible to cache

[Brian Stansberry (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBCACHE-1287?page=all ]

Brian Stansberry updated JBCACHE-1287:
--------------------------------------

    Summary: CacheLoader load operations cannot deserialize types not visible to cache  (was: CacheLoader load operations nnot deserialize types not visible to cache)

> CacheLoader load operations cannot deserialize types not visible to cache
> -------------------------------------------------------------------------
>
>                 Key: JBCACHE-1287
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1287
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Cache loaders
>    Affects Versions: 2.1.0.CR3
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>            Priority: Critical
>
> Cache loaders no longer are able to deserialize types not visible to the cache's classloader during load operations.
> New test org.jboss.test.marshall.CacheLoaderMarshallingTest shows the issue.
> When trying to deserialize, the cache loaders are calling into the marshalling code.  The marshalling code *always* sets the TCCL to the cache's class loader. So, if a caller app properly sets its TCCL to one that can load the app's custom types, tje marshalling code will undo this.
> If region-based marshalling is enabled, the correct classloader still isn't assigned, because the serialized data does not include the FQN information needed to find the correct region.  So again the cache's class loader is used.
> This is all a side effect of using the replication marshalling code for cache loader ops, which are somewhat different use cases.  When deserializing a replication message, the JGroups thread is unlikely to  have a TCCL that has visibility to the needed types.  Cache loader load operations usually have the correct TCCL in place. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira