JBoss development, A new message was posted in the thread "JBDEPLOY-226 - DeployerClient change extension": http://community.jboss.org/message/528169#528169 Author : Ales Justin Profile : http://community.jboss.org/people/alesj Message: -------------------------------------------------------------- I doesn't.   But it would definitely be good if it was the other way around - this feature needs circular resolving. Otherwise it doesn't make much sense, if the deployments are not actually moved into the state you wanted them to move. At least for the "valid" circular deployments -- which is often the case in OSGi -- according to TCK.   I don't see how checking at the end would help. They would still not be in the "right" state. Or are you saying Controller::change(deploymentContext, state) already knows how to resolve this? e.g. deployment A imports some B's packages, and vice versa, and afterwards we would expect both of them in past Describe state (or how do valid OSGi circular depencies look like?) -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/528169#528169