On Sat, Jun 18, 2011 at 9:23 AM, ant elder <[email protected]> wrote:
> For working out the smallest thing to restart i think the minimum may > be individual started composites. If there's a started composite from > an external .composite file or from a contribution thats exploded on > the file system then we can spot if the .composite file gets changed > and just restart the individual started composite. Even thats not > going to be totally perfect as it would missing restarts of things > using composites with <include> or <implementation.composite>. (maybe > it would be possible to fnd those by chasing all the pointers in > Tuscany, not sure, does any know if we maintain enough links to find > that?). It turned out that finding all started composites that used another composite was possible by chasing through all the includes and implementations.composites, so I've added a new Node method so you can restart those. ...ant
