well Scott is talking about just an abstract keyword (thread local) to identify a
given configuration. Is that what you are talking about.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3831621#3831621
Reply to the post :
Affirmative.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3831625#3831625
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3831625
---
This SF.Net email is sponsored by:
I've been thinking about this over the weekend, and what I think Im going to add is
the expansion of CFLOW. Currently CFLOW only looks at the Java call stack. I think I
will expand it to look at our metadata chain, or configuration domains.
Pretty much the tcl is set whenever a call enters into a container, be it jmx, ejb,
web. Its needed when transitioning from the microkernel into a deployment context that
can introduce new classes or class versions due to a deployment.
It would generally seem that the TCL is the more typical
