To run the demo, you will need at least two windows: one to peruse the cache contents (plus non-aop operations) and the other to operate the cache directly. Of course, you can also open more than one GUI window to see the cache replication at work to multiple members. You will also need to run the scripts under jboss-cache installation directory after you unzip the release package (jboss-cache-dist.zip). Due to the limitation of the GUI, please note that:
For each demo example, it'd be best if you re-start the whole setup.
While you can modify the cache content on the GUI window and it will show up on the BSH cache content (e.g., through cache.printDetails() ), this won't work on PojoCache demo. That is, you can only modify the cache content on the BSH window.
The two demo programs to run are:
On the first window for the GUI, type sh build.sh to see the available commands. To run the GUI, type sh build.sh run.demo . It will startup a PojoCache GUI. Later on, you can click on a node to view the the contents. Note that you can also add/modify the node contents for non-AOP cache entries. Since the GUI entry only accepts String for now, operation on aop cache from the GUI will not always work (unless it is a String type).
On the second window for the interactive Java commands, type sh runShellDemo.sh to fire off the BeanShell interactive command shell (you can use either ^D or ^Z in Windows and Unix to exit afterward). You can then read in the Java code scripts to showcase the cache capabilities (e.g., plain.bsh, aop.bsh, and aopWithTx.bsh). See the following for details.