The createNode(String... contributionLocations); operation sounds
reasonable. I'd like to make a list of what we have in various places
and what it's utility is. We already have several ways of creating
nodes through APIs and launchers and they are not consistent.

node-api/NodeFactory
    public Node createNode(URL configurationURL) {
        URL of a node config doc
    public Node createNode(InputStream is) {
        node config doc as a stream
    public Node createNode(String deploymentCompositeURI,
Contribution... contributions)
        deployment composite URI and list of contribution configurations
    public final Node createNode(String deploymentCompositeURI,
String[] uris, String locations[])
         ???
    public final Node createNode(String deploymentCompositeURI, String
locations[])
         ???
    public final Node createNode(Reader deploymentCompositeContent,
String[] uris, String locations[])
          ???
    public final Node createNode(String compositeURI, ClassLoader classLoader)
          ???
    public Node createNode(Contribution... contributions)
         list of contribution configurations
    public Node createNode(InputStream compositeContent,
Contribution... contributions)
         contributions and deployment composite in an input stream
    public Node createNode(Reader compositeContent, Contribution...
contributions)
        contributions and deployment composite in a reader
    public Node createNode()
        assume contrib is in current directory
   Seems to be a lot. What can we add/remove? Ant already suggested a
list of contribution locations.

domain-node/DomainNodeMain
    what args can be provided here?

node-launcher/NodeMain
    -nd
    -dm
    I'd be happy to loose this one. Extra code for very little value
IMHO. Just choose the appropriate launcher

node-launcher/NodeLauncher
    -c   compositeUri
    -n   node
    -s   service
    -t    time to live
    contribution...    a list of contribution locations
    are there other options?

node-launcher/NodeDaemonLauncher
   This this just started the node launcher and waits (with some fancy
shut down logic)

node-launcher/DomainManagerLauncher
   I assume this is not used at the moment?

node-launcher-equinox/NodeLauncher
    Has different options again so need to consolidate

Simon

Reply via email to