Lets first map what you're describing to JBoss Cache terminology. The stateless beans holds the business logic that interact wth the metadata that can be cache nodes within a tree. The user can alter those nodes specifically the user settings which can be stored as attributes of the nodes.
That's as far as I understand from your post. Can you provide more details for: anonymous wrote : | Changing the metadata takes some time (hours) and a lot of calls to the appserver but the application should still be up and running for other users. On the other hand, the cache is also needed to verify while changing. | so I can better answer you specific needs. Cheers, Hany View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3919903#3919903 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3919903 ------------------------------------------------------- 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 JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
