> > > Add the > > code that loads all contributions that are available from the file > system. > > Ant already has this code in various forms > > We can do simpler than load "all contributions that are available from > the file system" as the list of contributions to be loaded in a node is > determined from the composite allocated to it.
I was thinking specifically here about how the node is told which composite to load and subsequently how it physically locates the artifacts that are required. As we have disconnected nodes from the domain there is no service interface to call to pass this information. So my suggestion was to wrap the node with the code that can load information deployed via the file system in lieu of a service interface that tells the node what to do. > > > 3. As an experiment make a Domain that takes as input > > a - Contributions from disc (again can re-use Ant's contribution > loading > > code) > > I'm not too keen on scanning a disk directory as it doesn't apply to a > distributed environment, I'd prefer to: > - define a model representing a contribution repository > - persist it in some XML form > - provide a service to add/remove/update contributions > > Once we have that basic service in place, it'll be easy to develop a > program that watches a directory and drives the add/remove/update calls. This was just a step on the way suggestion to get the "repository" up and running quickly. We need to be able to read the model and the contributions themselves. In the spirit of keeping functions separate the mechanism by which the model and the contributions get to the repository is not connected to the way that they are read and processed. Regards Simon
