OK, this all looks good -- I'll move things in this direction and catch information in a wiki page that I think will end up as part of a top level samples README, as in the 1.x travel sample [2].
There's the basis of an async sample at [1] that needs to be brought into the proper directory. Kelvin. [1] http://svn.apache.org/viewvc/tuscany/sca-java-2.x/trunk/contrib/samples/async/ [2] http://svn.apache.org/viewvc/tuscany/sca-java-1.x/trunk/tutorials/travelsample/distribution/src/main/release/README?view=markup On Tue, Sep 14, 2010 at 9:16 AM, ant elder <[email protected]> wrote: > On Mon, Sep 13, 2010 at 5:19 PM, Florian MOGA <[email protected]> wrote: >> If I understand correctly, that makes the webapps folder a subcategory of >> getting-started. >> Just to sum it up, the new structure will be something like: >> + getting-started/ >> >> - helloworld-* >> + webapps >> >> - helloworld-* >> >> + running-tuscany >> >> - launcher-* >> >> + sca-features >> >> - implementation-* >> - binding-* >> >> + applications >> >> - store-* >> - calculator-* >> >> Where do the dosgi-* samples fit in (sca-features of applications)? What >> about the logging-scribe sample? >> This looks like a really intuitive structure, also not too much >> fragmentation but enough to make a clean separation. Are we considering >> promoting some itests to samples? There are some really good callback-api >> samples (that's what i've checked out some time ago) in the itest folder. >> > > Re the bit about making some itests samples, yes i agree, i think > there are several other things we don't have much in the way of > samples for yet which would be good to add, eg: > - callbacks > - scopes and lifecycle (i suppose thats mainly implementation.java) > - implemantation.composite > - contribution imports and exports > > ...ant >
