I've added a callback-api sample in the getting-started folder derived from the callback-api-basic integration test. Feel free to check it out and let me know what should be done next (declaration in parent poms, readmes, wiki page?).
I'll be looking for an itest that uses sca scopes. Let me know if you already know a simple one that would make a good getting started sample. @Ant: What kind of sample are you thinking of in order to show the sca-contribution.xml file? Can you give me an example (maybe an itest)? One detail that I've noticed is that we're having a lack for naming consistency for the samples (e.g. contribution-helloworld / helloworld-webapp). IMHO using a consistent naming (like helloworld-contribution / helloworld-webapp) is much more readable. If we all agree with this I can make the necessary changes during the morning as we've got the time difference and there won't be any overlapping commits. On Mon, Sep 27, 2010 at 11:03 AM, Simon Laws <[email protected]>wrote: > On Mon, Sep 27, 2010 at 8:49 AM, ant elder <[email protected]> wrote: > > On Sat, Sep 25, 2010 at 6:27 PM, Florian MOGA <[email protected]> > wrote: > >> Hi Kelvin, > >> > >> Given the agreed directory structure, I'd also include in the > >> getting-started directory the samples illustrating callbacks and scopes > >> which we were thinking to promote from the itest folder. Thoughts? Which > of > >> them do you think would be most suitable? > >> > > > > Yes i think that would be good, I'd envisaged getting-started > > including enough to get a bit of a taste of what SCA is about, so the > > concepts we think are important. I was thinking things like using > > contributions and the sca-contribution.xml file, composites with some > > implementation and binding types along with the basic assembly > > constructs like components, services and references. Scopes and > > callbacks come up a lot on the user list so it would be good if they > > could fit in too, though i can see we do need to find a balance and > > have things to go in the learning more folder. > > > > ...ant > > > > Sounds good. I think the balance would be that in getting started we > can show the user how to use a binding or an implementation type but > that we don't have to show them how to use all the different bindings > or implementation types. Similarly for other sca features such as > callbacks and scopes, we should show them what they do but leave > demonstration of the combination/extent of configuration options to > the learning more section. As Ant says, demonstrate the important > features that allow a user to get started. > > Simon > > -- > Apache Tuscany committer: tuscany.apache.org > Co-author of a book about Tuscany and SCA: tuscanyinaction.com >
