[
https://issues.jboss.org/browse/ISPN-1834?page=com.atlassian.jira.plugin....
]
William Burns commented on ISPN-1834:
-------------------------------------
There is an issue with how the lookup is currently implemented in the hibernate side
(v4.1)
I have created
https://hibernate.onjira.com/browse/HHH-7166 with a patch that has a fix to
get around it until this issue is completed to have a more complete fix.
Improve the way custom objects are injected into
ExtendedModuleCommandFactory impls
-----------------------------------------------------------------------------------
Key: ISPN-1834
URL:
https://issues.jboss.org/browse/ISPN-1834
Project: Infinispan
Issue Type: Enhancement
Reporter: Galder Zamarreño
Assignee: Manik Surtani
Fix For: 6.0.0.FINAL
Retrieving the ExtendedModuleCommandFactory associated with a cache manager is a PITA
right now, you have to do:
{code}GlobalComponentRegistry globalCr =
cache.getComponentRegistry().getGlobalComponentRegistry();
// TODO: This is a hack, make it easier to retrieve in Infinispan!
return (CacheCommandFactory) ((Map)
globalCr.getComponent("org.infinispan.modules.command.factories"))
.values().iterator().next();
{code}
Provide a cleaner way of initialising cache command factories for custom objects that the
factory can plug into the remote commands. Example: evict all in 2LC where commands need
to know the cache region (a Hibernate construct) on which to operate on.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira