Is there a reason why DemandDependencyItem doesn't set demand as iDependOn in its constructor? | public DemandDependencyItem(Object name) | { | super(name, null, whenRequired, null); | Since then we get a lot of these | Object iDependOn = item.getIDependOn(); | if (iDependOn == null) | { | dependency = "<UNKNOWN>"; | actualStateString = "** UNRESOLVED " + item.toHumanReadableString() + " **"; | } | in DeployersImpl:checkControllerContext View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4140958#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...