Basic steps: 1) Create a -service.xml file (say "mycacheaop-service.xml") to configure your cache. http://docs.jboss.com/jbcache/1.2.4/TreeCache/html/[/url] and [url]http://docs.jboss.com/jbcache/1.2.4/TreeCacheAop/html/ have lots of details on this that I'm not going to go into. Note section 6.1 of the TreeCacheAop doc on what you need to do to make your MBean use TreeCacheAop.
2) "mycacheaop-service.xml" goes in the /server/all/deploy directory, or you can package it in an ear or sar bundled with your client code. You can find docs online on how to package a service in an ear. 3) Chapter 12 of the TreeCache doc describes how to access your cache from client code inside JBoss. If you want your client code to work in an envrironment where the cache may not be an bmean, I recommend you use the JNDI approach -- look up the cache in JNDI. The docs give an example mbean config for binding the cache in JNDI; you can add something like that to the bottom of your "mycacheaop-service.xml". Note that the example is written for TreeCache; where you see "TreeCacheMBean" you need to use "TreeCacheAopMBean", both in the mbean config and in your client code. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3920129#3920129 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3920129 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
