In attending AOSD, I found that others implement CFLOW differently than I have. I use new Throwable().getStackTrace and parse the stack. This is slow as balls. The way others use it is that they increment a ThreadLocal counter at the execution point of a element in the cflow expression.
The debate is, yes, the ThreadLocal approach is a much much much faster implementation of cflow, but if cflow check is a rare occurance, then you have slowed down execution joinpoints signficantly. I guess the answer is to do either or and through configuration turn on/off this optimization. Bill <a href="http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3827734#3827734">View the original post</a> <a href="http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3827734>Reply to the post</a> ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
