anonymous wrote : I think of a context as a closure over a scope.
yikes! But that's not what I'm getting at - mainly, it's about simplifying the
number of terms used to express the same thing.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3968140#3968140
I think I usually use context when I'm thinking of multiple instances of the
same scope, and scope when I'm thinking of different scope granularities. But
I'm not always very strict about that, and the docs may not always adhere to
that.
So for example, there is a many-to-one mapping between
I think of a context as a closure over a scope. Scopes are static constructs
in the source, contexts are instances in the runtime. I think context is one
of the most overloaded terms in programming, but seam's use is pretty
consistent with the way JEE (or at least the servlet spec) uses it.