Hi

  Currently, the SCADomain uses the following signature for newInstance :
     public static SCADomain newInstance(String domainURI, String
contributionLocation, String...composites)
  And sample applications are using like :
     SCADomain domain = SCADomain.newInstance("http://calc";, ".", "
Calculator.composite");

  I have a quick question :

  - Why we would need to specify multiple composites from one same
contribution ? Currently we have the getDeployables from a contribution that
would give you all deployable composites based on contribution metadata side
file ( sca-contribution.xml), or in the case that file is not available, it
would promote all composites to be deployable. Can that be used instead ? If
so, do we need to pass the deployable composites at al ?

  Also, I'd suggest to have something more towards the code below :

     SCADomain.newInstance(domainURI);
     SCADomain.addContribution(uri, location);
     SCADomain.addComposite(composite);

  This would probably also be more aligned to the spec...

Thoughts ?

--
Luciano Resende
http://people.apache.org/~lresende <http://people.apache.org/%7Elresende>

Reply via email to