[infinispan-issues] [JBoss JIRA] (ISPN-1764) Remove threadLocal in org.infinispan.context.AbstractInvocationContextContainer

Mircea Markus (JIRA) jira-events at lists.jboss.org
Tue Jul 2 03:15:21 EDT 2013


     [ https://issues.jboss.org/browse/ISPN-1764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mircea Markus updated ISPN-1764:
--------------------------------

    Fix Version/s:     (was: 6.0.0.Final)

    
> Remove threadLocal in org.infinispan.context.AbstractInvocationContextContainer
> -------------------------------------------------------------------------------
>
>                 Key: ISPN-1764
>                 URL: https://issues.jboss.org/browse/ISPN-1764
>             Project: Infinispan
>          Issue Type: Enhancement
>            Reporter: Sanne Grinovero
>            Assignee: Manik Surtani
>
> The javadocs in org.infinispan.context.AbstractInvocationContextContainer mention:
> {quote}// See ISPN-1397.  There is no real need to store the InvocationContext in a thread local at all, since it is passed
>    // as a parameter to any component that requires it - except for two components at the moment that require reading
>    // the InvocationContext from a thread local.  These two are the ClusterCacheLoader and the JBossMarshaller.  The
>    // former can be fixed once the CacheStore SPI is changed to accept an InvocationContext (see ISPN-1416) and the
>    // latter can be fixed once the CacheManager architecture is changed to be associated with a ClassLoader per
>    // CacheManager (see ISPN-1413), after which this thread local can be removed and the getInvocationContext() method
>    // can also be removed.
> {quote}

--
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: http://www.atlassian.com/software/jira


More information about the infinispan-issues mailing list