I renamed the JMX-based provider classes as described above and added the JNDI-based providers and the default versions that instantiate a cache from a config file.
This has been released as 1.0.0.GA. I decided not to do CR1; Prabhat if you see issues we can do a 1.0.1.
I can blog about it when I get back, or, Galder if you feel like blogging, go for it; you did most of the work and can rightly take the glory if you wish.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4173130#4173130
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4173130
"bstansberry(a)jboss.com" wrote : Prabhat,
|
| One thing I'd like to change before cutting the release would be the name of the provider classes: from "org.jboss.hibernate.jbc.cacheprovider.(Optimistic)TreeCacheProvider" to "org.jboss.hibernate.jbc.cacheprovider.(Optimistic)JmxBoundTreeCacheProvider". Will that mess you guys up too much?
|
I think it should be okay.Only reference of this class I have in portal is in few hibernate configuration files
| <property name="cache.provider_class">org.jboss.hibernate.jbc.cacheprovider.TreeCacheProvider</property>
| <property name="treecache.mbean.object_name">portal:service=TreeCache,type=hibernate</property>
|
So it will be simply changing value of cache.provider_class. Once you have the new jar, please let me know and I can do a quick sanity check before you leave so that you have more pleasant vacation. :-)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4173127#4173127
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4173127