"adrian(a)jboss.org" wrote : | For ease of use it probably is, but making it work is requiring too many hacks | Ok, moving Controller looks kind of hackih, but it is used transparently regarding previous code. "adrian(a)jboss.org" wrote : | and I have a feeling that Ales is doing it wrong anyway or has at least | misunderstood part of it (Given some of the problems he is reporting). | My problems are mainly from missing API point of view - UID name, ScopeKey as param, AOP scoping domain, ... Or which part you think is really misunderstood? "adrian(a)jboss.org" wrote : | The alternate approach would be to move the scoping of kernels to the deployers. | i.e. The MC can support scoped kernels but you have to use an api | to configure them. | | The deployment chain would then look something like: | 1) Parsing as now (for POJOs - BeanDeployer) | 2) ClassLoading deployer (as now or replaced with OSGi style) | 3) Component Deployer (for POJOs KernelDeploymentDeployer) | 4) Scoping Deployer (NEW looks at BeanMetaData and creates ScopedKernel) | 5) Real Deployer (as now BeanMetaDataDeployer - but deploys into ScopedKernel) | | This gives a cleaner api and probably makes it easier to override scoping rules. | | The downside is that you don't get scoping out of the box, you either | have to use the deployers or write your own scoping config code. We can probably support both. Just need to work on the use cases of current impl - something we said before I went and hacked this initial code. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4022431#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...