With all the 2.x changes going on and runtime starting discussion i was
wondering about changing some of our samples so that most samples create
proper SCA contribution jars, they get run by deploying the contribution to
a runtime, they wouldn't include the client impl which invokes the sample
within the contribution jar, and maybe also have samples use the
contributions from other samples. It would need a launcher if we did it that
way (like what is being discussed on the runtime launching thread), and we'd
need separate client samples.

It might make the very simplest samples slightly more complicated, but it
makes the sample contributions more reusable across the various runtime
environments and would demonstrate how to use domains with multiple
contributions and composites and how to swap around different binding and
implementation types.

I'm in two minds if it would be better than the current approach, what do
others think?

   ...ant

Reply via email to