Re: [wildfly-dev] Service assumptions and the web profile

> One obvious question with this scheme is: what happens when Y is added, > after the fact? The answer to this question depends on X. X must, in > the same transaction, detect the addition of Y and decide what to do. > Several actions are possible, depending on how X works and how its > dependency on Y works. Options include automatically removing and > rebuilding services with the new dependency, retroactively modifying X > in some way so as to update it without stopping it, or simply ignoring > the addition of Y, using a "reload-required" or similar state to > indicate to the user that the running system is inconsistent with the > stored model. > > I know we don't really have any APIs to directly facilitate these > concepts, but this is a part of what the management SPI redesign is all > about. In the new model, one will be able to express optional > dependencies at a resource level rather than a service level. Jeff Mesnil -- I'm curious how useful the internal notification stuff you've added in the existing code will be for this use case. Prior to that there was nothing at all that X could count on to become aware of the later addition Y.