> - createNode(URI uri, String... contributionLocations);
> where the uri is the config uri that can be used to configure things
> like the domain name and registry. That would match the SCAClient API
> that takes the the similar uri to connect to the running services
+1 It would seem sensible that all the atributes (that started this
discussion) should be able to be provided via the API as well as via
the XML file. So we should support uri, domainURI, domainRegistryURI
(I haven't gone back and looked at the difference yet)
>
> - it would useful and consistent to have a way to use Nodes with the
> objects created from the Deployer so for example you can doing things
> like Deployer.loadContribution, fiddle about with the Contribution and
> then use that object in a Node. I'm not suggesting a method signature
> for this yet as this opens up quite a lot of interesting options. For
> example, all the NodeFactory methods about attaching or adding
> deployment composites could then be done via the Deployer instead of
> all the overloaded createNode methods. To do this well requires quite
> a lot of changes to the Node APIs but after some playing around it
> looks to me like it could make the APIs much cleaner with the simple
> uses clear and obvious and the more complex cases more consistent and
> powerful.
Interesting. Sounds like you have examples. Can you post? Need to be
careful about dependencies, i.e. to use the API what dependencies do
you need to include. We have a workspace manager in 1.x that combines
deployer type features with the ability to interact with the
runtime/exntrsion points. No precisely what you are suggesting but I
remember there were a lot of dependencies. Let discuss more and see
where it goes.
>
> - rename createNode(URL) to match the other loadConfiguration method,
> or rename both to something like createNodeFromConfig
Didn't spot those methods down at the bottom of NodeFactory. So we also have...
public abstract Node createNode(NodeConfiguration configuration);
node configuration object
public abstract NodeConfiguration loadConfiguration(InputStream
xml, URL base);
XML = node config xml? base = ?
createNode would be more consistent
>
> Some to remove:
> - all the ones using classloaders
> - the Client Interface and just add the getService method to Node
Can we return an SCA client factory instance for the node
> - the destroy method
> - the getInstance(String domainURI) as there's the createNode that
> includes the URI
>
> ...ant
>
