tuscany-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ant elder <ant.el...@gmail.com>
Subject Re: Node2 vs Node, parallel universes? Sample tuscany launcher shell
Date Thu, 08 Jul 2010 15:43:02 GMT
On Thu, Jul 8, 2010 at 4:31 PM, Raymond Feng <enjoyjava@gmail.com> wrote:

> I think it would be a good idea to agree on the commands for shell. This
will help us understand how users use SCA. Then it can be translated into a
set of API/SPIs.
>

Here's what the shell module currently has:

(the easiest way right now to see it for yourself is by building
shades\base-nodep and doing java -jar
target\tuscany-base-nodep-2.0-SNAPSHOT.jar)

>java -jar target\tuscany-base-nodep-2.0-SNAPSHOT.jar
Apache Tuscany Shell (2.0-SNAPSHOT 961743 20100708-1353)
Commands:

  help
  install [<uri>] <contributionURL> [-norun -metadata <url> -duris
<uri,uri,...>]
  installed [<contributionURI>]
  remove <contributionURI>
  addDeploymentComposite <contributionURI> <contentURL>
  printDomainLevelComposite
  start <curi> <compositeUri>
  status [<curi> <compositeUri>]
  stop [<curi> <compositeUri>]

Use Tab key for command and argument completion
For detailed help on each command do 'help <command>', for help of startup
options do 'help startup'

=> help install
  install [<uri>] <contributionURL> [-norun -metadata <url> -duris
<uri,uri,...>]

  Creates an installed contribution with a supplied root contribution,
installed at abase URI.

  Arguments:
     uri - (optional) the URI (name) to use for the contribution. When no
uri is specified
              a default URI is used derived from the contribution URL
     contributionURL - (required) the URL to the contribution to install
     -norun - (optional) do not start any composites listed as deployable in
the sca-contribution.xml file
     -metadata <url> - (optional) the URL to an external contribution meta
data document that should be
              merged into any existing sca-contributions.xml file within the
contribution.
     -duris <uri,uri,...> - (optional) specifies the URIs of contributions
that are used to resolve the
              dependencies of the root contribution and other dependent
contributions.
              When not specified all installed contributions are used to
resolve dependencies.
=> help installed
  installed [<contributionURI>]

  Shows information about the contributions installed on this node,
  including the contribution URI and location along with the URI
  and QName of any composites within the contribution

  Arguments:
     contributionURI - (optional) the URI of an installed contribution
=> help remove
  remove <contributionURI>

  Removes an installed contribution

  Arguments:
     contributionURI - (required) the URI of an installed contribution
=> help addDeploymentComposite
  addDeploymentComposite <contributionURI> <contentURL>

  Adds a deployment composite using a supplied composite ('composite by
value' - a data
  structure, not an existing resource in the Domain) to the contribution
identified by a
  supplied contribution URI. The added deployment composite is given a
relative URI that
  matches the @name attribute of the composite, with a '.composite' suffix.
Since all composites
  run within the context of an installed contribution (any component
implementations or other
  definitions are resolved within that contribution), this functionality
makes it possible
  for the deployer to create a composite with final configuration and wiring
decisions and add
  it to an installed contribution without having to modify the contents of
the root contribution.

  Arguments:
     <contributionURI> - (required) the URI of an installed contribution
     <contentURL> - (required) the location of the composite
=> help printDomainLevelComposite
  printDomainLevelComposite

  Not yet implemented

  Arguments:
     none
=> help start
  start <curi> <compositeUri>

  Starts a composite.
  The composite is added to the domain composite with semantics that
correspond to the domain-level
  composite having an <include> statement that references the supplied
composite. All of the composites
  components become top-level components and the component services become
externally visible
  services (eg. they would be present in a WSDL description of the Domain).

  Arguments:
     curi - (required) the URI of an installed contribution
     compositeUri - (required) the URI of a composite
=> help status
  status [<curi> <compositeUri>]

  Shows the status of the Node, listing for each deployed composite its
  contribution URI, the composite URI, and the composite QName.

  Arguments:
     curi - (optional) the URI of an installed contribution
     compositeUri - (optional) the URI of a composite
=> help stop
  stop [<curi> <compositeUri>]

  Stops this Node or individual composites and contributions in the Node.
  If a composite URI is specified then the composite is removed from the
Domain Level composite
  This means that the removal of the components, wires, services and
references originally added
  to the domain level composite by the identified composite. If a
contribution URI is specified
  without a composite URI then all deployed composites composites in the
contribution are stopped.
  If no contribution URI is specified then the entire Node is stopped and
the Shell exits.

  Arguments:
     curi - (optional) the URI of an installed contribution
     compositeUri - (optional) the URI of a composite
=>

   ...ant

Mime
View raw message