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?
Great initiative with the document
I'm making a single wiki page [1] atm, which we can ship/reference as
we like (e.g. PDF). I think I have just got to the point where the
doc structure matches the directory structure. Now its fill in the
blanks time :)
Kelvin
[1] https://cwiki.apache.org/confluence/display/TUSCANYxDOCx2x/Sample
Hi Florian
there seemed to be consensus that we wanted a flatter structure, and
the split wasnt helpful, so everything that was in one of the features
directories is now in the learning-more directory
On Sat, Sep 25, 2010 at 6:03 PM, Florian MOGA wrote:
> Hi
>
> I'm on vacation and a bit out-da
+1 for single pdf. I think the chances of it getting out-dated or not
reflecting the current structure of the directories are considerably less
than multiple readme-s.
On Sat, Sep 25, 2010 at 7:03 PM, Florian MOGA wrote:
> Hi
>
> I'm on vacation and a bit out-dated with the mailing list but if w
Hi
I'm on vacation and a bit out-dated with the mailing list but if we're still
up to making a clean separation between sca and tuscany features, the
following names came to me which seem self explanatory: oasis-spec-features
/ extra-features.
On Fri, Sep 24, 2010 at 6:09 PM, kelvin goodson wrote
Hi to all,
I'm developing a new implementation type for Tuscany 1.x, based on ASM, I've
been successfully in calling services and introspecting references and
properties, but I don't know how to get the current wiring from the running
composite, so that I can match them and call the corresponding s
