Hi Melterm, you would have to wrap execution in some kind of class of your own of course if you want to intercept all calls. In my current project - for various reasons - I had build a MDB that does all the signaling so I had a single point of entry. I even go further do encapsulate a lot of 'magic' from developers, but that won't help you much...
My other point was the neccessity of persisting in all nodes. What is the scope of your transactions? Does it span all 20 nodes? If so, do you need to persist everytime, as it would only be flushed / commited once when returning from the last node? If your nodes / actions are long running themself: - do they run in seperate transactions? - is persistence really a performance hit (if the action itself is longrunning already)? Just my 2 cents.. Rainer View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3911392#3911392 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3911392 ------------------------------------------------------- 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://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
