As you mentioned, this might make our samples more complex then expected from a new user.
What would be the user experience here ? Maybe we could do something with the demos, that are already more complex and try to demonstrate a more realistic user scenario ? On Wed, Jan 21, 2009 at 8:55 AM, ant elder <[email protected]> wrote: > 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 > > -- Luciano Resende Apache Tuscany, Apache PhotArk http://people.apache.org/~lresende http://lresende.blogspot.com/
