"adrian(a)jboss.org" wrote : dependency with knock on affects into kernel
How would you then introduce this information?
OK, it should be more generic that simple 'local', since, as you said, controller
scope could/should be more generic (peer, hierarchy, ...).
To actually get the context from the wanted scope, some simple interface could be
introduced.
| public interface GraphController
| {
| ControllerContext getContext(Object name, ControllerState state, LookupStrategy
strategy) throws Throwable
| }
|
Where LookupStrategy would dictate how lookup should be done, e.g. local first, local
only, parent only, ...
If underlying Controller didn't impl this, we could either throw error or silently
fall-over to plain context lookup.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4162503#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...