Simon Laws wrote:
[snip]
How about the following as some first steps.
1. Disengage the Node from the domain in the way that it is connected at the
moment leaving the Node able to load Contributions and start composites as
it does currently in stand alone mode. Doing this we remove the sca
application that is used to connect the node to the domain and the need to
pull in WS, JSON etc that came up on another thread.
+1 to disengage all the magic domain/node connections.
2. Wrap the Node in the first run options we want to test with (standalone
and tomcat webapp would give us enough to try most of the samples).
I'd like to focus on the J2SE standalone option as trying to tackle many
options before having the simple one really figured out will create a mess.
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.
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.
b - a topology file something like [1]
and produces as output
c - a list of which contributions need to be copied to which node and
appropriate warnings about missing dependencies
d - updated contributions/composites so that references that refer to
services in remote nodes have absolute URLs written in to appropriate
bindings.
+1 to the general ideas but I really want to decouple b, c, d as they
are independent steps.
We also have most of the code already to do a-d in various places. d is
the trickiest bit but provides the ideal opportunity to tidy up the binding
URL calculation story.
The less code the better... We may be able to reuse a little bit but we
can cover the scenario I've tried to describe with much less code than
we currently have :)
[1] http://www.mail-archive.com/[email protected]/msg26561.html
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
