[jboss-dev-forums] [Design the new POJO MicroContainer] - Re: Checking DeploymentContext for failures

[adrian@jboss.org]

We're having this discussion in two places, let's keep it here. ;-)

You already know the context name of the deployment controller
context and how to retrieve it (assuming it has got as
far as creating it :-)

It's an implementation detail of the class you are changing.

The ones you don't know about are those created by
the deployers, i.e. the [Kernel|Service]ControllerContext

You just need those deployers that create them to record
them somewhere for you to check.

Looking at the attachments can even be misleading, because
the attachment may exist (created by the parsing
deployer) but it never got as far as actually
registering them in the controller.

Or maybe the deployer tried to register it, but found it
was a duplicate (already registered).
So you'd actually be looking at the wrong context!

Besides it's over engineered for the purpose.
You just want a set of names that were definitely
registered in the controller for that deployment.

Once you have those, you also need to recurse through the
DependencyInfo looking to find the possible root cause 
for failed contexts.

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

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