[
http://jira.jboss.com/jira/browse/JBCACHE-1023?page=comments#action_12360240 ]
Manik Surtani commented on JBCACHE-1023:
----------------------------------------
From jbosscache-dev mail list
http://lists.jboss.org/pipermail/jbosscache-dev/2007-April/001330.html
agreed to expose injecting of a channel via the runtime config:
cache = DefaultCacheFactory.createCache(config, false);
cache.getConfiguration().getRuntimeConfiguration().setChannel(myChannel);
cache.start ();
Inject preconfigured JGroups Channel from external implementation
-----------------------------------------------------------------
Key: JBCACHE-1023
URL:
http://jira.jboss.com/jira/browse/JBCACHE-1023
Project: JBoss Cache
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Clustering
Reporter: Bill Middleton
Assigned To: Manik Surtani
Fix For: 2.0.0.CR1, 2.0.0.GA
Attachments: patch.txt
The current cache implementation contains and manages its own JGroups Channel. It would
be useful for those of us using the Cache outside of a full app server to be able to
inject our own pre-configured JChannel to the Cache.
The original discussions regarding this issue occured on the dev mailing list during
April 2007
http://lists.jboss.org/pipermail/jbosscache-dev/2007-April/thread.html
A patch is (will be) attached which implements the desired functionality by providing an
extra method in the DefaultFactory and a new constructor for CacheImpl. This makes
everything "work ok for me", using either multiplexed or "ordinary"
JChannels. Unknown if or whether this patch is an appropriate fix.
--
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