You'd need to refactor all the unit tests to use this mechanism of
cache construction though ... is this for after alpha2?
--
Manik Surtani
Lead, JBoss Cache
JBoss, a division of Red Hat
Email: manik(a)jboss.org
Telephone: +44 7786 702 706
MSN: manik(a)surtani.org
Yahoo/AIM/Skype: maniksurtani
On 3 Jan 2007, at 15:38, Vladimir Blagojevic wrote:
Just an update on what I am doing regarding JBCACHE-840. The best
approach seems to be to create UnitTestCacheFactory with following
signatures:
Cache createCache(Configuration c);
Configuration createConfiguration(int type); //type=sync|async
Cache createCache(int type); //type=sync|async
UnitTestCacheFactory will have inner parser class that that is a
subclass of XmlConfigurationParser. This subclass will read cache
configuration file which will have all supported jgroups stacks.
Something similar to mux stacks.
When invoking create methods of UnitTestCacheFactory jvm parameter
will
be consulted to decide whether to crate udp, tcp, tcp-nio stack and so
on.
If you have some suggestions shoot back.
_______________________________________________
jbosscache-dev mailing list
jbosscache-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosscache-dev