[jboss-dev-forums] [Design the new POJO MicroContainer] - Re: Deployers Ordering Issue

richard.opalka@jboss.com do-not-reply at jboss.com
Thu Jun 25 10:25:24 EDT 2009


"alesj" wrote : Although thinking about it.
  | I actually don't see why it wouldn't be valid.
  | 
  | Perhaps you really want what is stated there,
  | that in that particular stage, you have the explicit input/output ordering.
  | Regardless that the stages don't match,
  | e.g. output coming in later stage than the input
  | whereas this would come in play when new deployer with matching input/output is added

This is exactly the reason why I'm saying:
ad1) You can't validate properly deployer dependencies/requirements in insert phase (domino algorithm tries to do it - wrongly)
ad2) You can do it properly only in method DeployersImpl.getDeployersList(String stageName) (i.e. sort lazily on retrieval and detect errors here and not in insert phase)

It's because you don't know the order in which deployers will be added to deployers chain. IOW you can't validate/sort untill you have full chain.

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

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



More information about the jboss-dev-forums mailing list