User development,
A new message was posted in the thread "Undemanding Dependencies":
http://community.jboss.org/message/521572#521572
Author : David Lloyd
Profile :
http://community.jboss.org/people/david.lloyd@jboss.com
Message:
--------------------------------------------------------------
alesj wrote:
> In this case, what do you consider "-->" to mean?
>
A --> B, by this I mean that from A you can get a hold of B.
> I'm producing a BeanMetaData but after that I don't have any control over
how the beans are installed. I don't see any way to get a ControllerContext or
DependencyInfo off of a BMD. I think I see what you're getting at (using a lifecycle
callback on the parent to enable the child), I just don't see how to connect the
dots.
Even from BMD you have access to underlying ControllerContext, you just don't know it
yet. :-)
It's the MetaDataVisitorNode methods, that get you that, we just need to properly
override them.
BMD.initialVisit(MDVN node) <-- override this
ControllerContext context = node.getControllerContext();
DependencyInfo info = context.getDependencyInfo();
LifecycleCallbackItem item = new MyStarterLCI(); // this is what starts As
info.addLifecycleCallback(item);
Does this make more sense?
Ah, I see. However I can't affect the parent's
BMD in this case - only the child's.
--------------------------------------------------------------
To reply to this message visit the message page:
http://community.jboss.org/message/521572#521572