Hi Guilherme On Mon, Jun 13, 2011 at 4:02 PM, Guilherme Armigliatto <[email protected]> wrote: > Hello, > > I am a little behind the schudule because I am finishing my master course. > Fortunately it's finish at friday 17th! Then I will have more time to > dedicate to GSoC. =)
So 17th is a big day. Good luck! > > One interesting thing I read about SCALA is that it has elements that can be > used as basis for a service-oriented software component model > implementation. In this way, a first mapping between SCA elements and SCALA > elements could be: Sounds like a good list to start with to me... > - components -> classes and traits Would you consider an interface.scala as well as in implementation.scala? > - services -> concrete members of a class ok > - references -> deferred members of a class not sure about this one. Why deferred members? In SCA we reference refer to know services with a well defined interface. In Java, for example, a reference would be a member variable. It's identified as a reference either through direct annotation or because it's name matches a reference in the component definition in the composite file. > - composition -> mixins not sure about this either. I can see this used as a composition mechanism in a pure SCALA environment but in this case we're putting SCALA inside SCA which has it's own composite mechanism as defined by the assembly model. I.e. references can be wired to services within a composite and components can be implemented using other composites. > > I am working on this and I will provide some pack soon. Excellent, look forward to it. > > Regards, > Guilherme > > --- > Guilherme Moraes Armigliatto > Master Degree Student > Reasoning for Complex Data (RECOD) > Institute of Computing (IC), University of Campinas (UNICAMP) > Campinas, SP, Brazil > > Simon -- Apache Tuscany committer: tuscany.apache.org Co-author of a book about Tuscany and SCA: tuscanyinaction.com
