[jboss-dev-forums] [Design the new POJO MicroContainer] - Re: Dependencies from scoped to global

[kabir.khan@jboss.com]

I think/hope this is the last hurdle for me to get scoped aop working. Deploy works fine, undeploy doesn't as described above.

Here's a quick hack for you :-) For my use case the scoped bean is an aop interceptor, and the global is a bean that gets injected into the interceptor. The interceptor is installed into a scoped controller by the aop deployer with a unique prefix/name. So we could look at the child controllers for a bean with that name if this call returns null. 

  | ControllerContext dependent = getContext(item.getName(), null);
  | 
This would work for aop, but could break other things if names are not unique. You did however recommend unique names due to shortcomings in AbstractController.uninstall(), so "other things" using scoping might be broken anyway?

I'm not familiar with this part of the code, so the rest of this post is me guessing :-) Who populates DependencyInfo.dependsOnMe? I would assume it happens when describing the side who has the dependency? i.e. the scoped bean who has a dependency on the global one? If that is correct, could/should not the controller be known for the dependencies?

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171271#4171271

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4171271