Not sure about this DefaultSCAContainer thingy - that's not something that's in trunk.

Based on the deployment model in the spec, contribution is totally separate from running components. Contribution is about defining type information in the domain, something that happens once (per type); running components is about creating instances of those types, something that happens many times.

So from the command line, to make a contribution the user would do something like:
  $ java -jar contribute myContribution.jar ...
which would contribute that jar to the local domain (perhaps with command line args to contribute it to other domains).

Of course, this is just the command line form admins might use - we'd want to offer alternatives such as a Maven plugin, Ant task or IDE integration. These would all be wrappers around the ContributionService.

With this in place, we should be able to migrate the launcher to a mode where the user just needs to specify the component to launch:
  $ java -jar launcher myComponent args...
and the runtime does the rest.

--
Jeremy

On Feb 25, 2007, at 1:00 PM, Luciano Resende wrote:

I want to start getting the Contribution service integrated to the process of running components, and I was thinking to give it a try by integrating the service with the new DeafultSCAContatiner that some sample apps in the integration branch is using. I think the idea is to stop using the launcher to consume the application SCDL, and ask the Contribution service to process
the application as a contribution.

from:
component = launcher.bootApplication("application", applicationSCDL);

to maybe:
URI appURI = this.contributionService.contribute(contributionLocation,
false);
...

Today, when you ask the contribution service to consume an application, you will get back an URI, that is an ID for that contribution. So, my question is, how the external world would get access to the model objects created during the loading phase from the contribution service ? Is the contribution
service responsible to register these model objects
(e.gcomponentDefinition) into some specific model repository (
e.g the domain) ? and If so, how do I got about doing this ?


Could someone please share some ideas, or more concrete example on how I'd
go about integrating the Contribution service into the big picture ?

--
Luciano Resende
http://people.apache.org/~lresende


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to