You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by Guilherme Armigliatto <gu...@gmail.com> on 2011/06/13 17:02:55 UTC
[GSoC] scala.implementation status
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. =)
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:
- components -> classes and traits
- services -> concrete members of a class
- references -> deferred members of a class
- composition -> mixins
I am working on this and I will provide some pack soon.
Regards,
Guilherme
---
Guilherme Moraes Armigliatto
Master Degree Student
Reasoning for Complex Data (RECOD)
Institute of Computing (IC), University of Campinas (UNICAMP)
Campinas, SP, Brazil
Re: [GSoC] scala.implementation status
Posted by Douglas Leite <do...@gmail.com>.
Hi Guilherme,
Take a look at [1] and [2], I think it might be useful for you when writing
a new implementation component type.
Regards,
[1]
http://tuscany.apache.org/sca-java-extension-development-guide.data/ExtendingTuscany1.pdf
[2]
http://tuscany.apache.org/mike-edwards-ramble-through-adding-a-new-implementation-type.html
On Mon, Jun 20, 2011 at 4:03 AM, ant elder <an...@gmail.com> wrote:
> Hi Guilherme,
>
> That sounds like a comprehensive and indepth approach to the SCA Scala
> integration. You may find it a little daunting working out where and
> what in the Tuscany code you need to change and add to do it all
> though so I wonder if you should start with something quite simple
> like a very basic helloworld type app and get some of that going as a
> first step. We have a Scala helloworld from when a user was asking
> about it which just uses the standard SCA <implementation.java> so how
> about taking that and getting it to work using an
> <implementation.scala>? You can find some emails about that sample at
> http://apache.markmail.org/message/zswdmbimo5al3erf
>
> ...ant
>
> On Mon, Jun 13, 2011 at 4:02 PM, Guilherme Armigliatto
> <gu...@gmail.com> 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. =)
> >
> > 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:
> > - components -> classes and traits
> > - services -> concrete members of a class
> > - references -> deferred members of a class
> > - composition -> mixins
> >
> > I am working on this and I will provide some pack soon.
> >
> > Regards,
> > Guilherme
> >
> > ---
> > Guilherme Moraes Armigliatto
> > Master Degree Student
> > Reasoning for Complex Data (RECOD)
> > Institute of Computing (IC), University of Campinas (UNICAMP)
> > Campinas, SP, Brazil
> >
> >
>
--
Douglas Siqueira Leite
Re: [GSoC] scala.implementation status
Posted by ant elder <an...@gmail.com>.
Hi Guilherme,
That sounds like a comprehensive and indepth approach to the SCA Scala
integration. You may find it a little daunting working out where and
what in the Tuscany code you need to change and add to do it all
though so I wonder if you should start with something quite simple
like a very basic helloworld type app and get some of that going as a
first step. We have a Scala helloworld from when a user was asking
about it which just uses the standard SCA <implementation.java> so how
about taking that and getting it to work using an
<implementation.scala>? You can find some emails about that sample at
http://apache.markmail.org/message/zswdmbimo5al3erf
...ant
On Mon, Jun 13, 2011 at 4:02 PM, Guilherme Armigliatto
<gu...@gmail.com> 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. =)
>
> 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:
> - components -> classes and traits
> - services -> concrete members of a class
> - references -> deferred members of a class
> - composition -> mixins
>
> I am working on this and I will provide some pack soon.
>
> Regards,
> Guilherme
>
> ---
> Guilherme Moraes Armigliatto
> Master Degree Student
> Reasoning for Complex Data (RECOD)
> Institute of Computing (IC), University of Campinas (UNICAMP)
> Campinas, SP, Brazil
>
>
Re: [GSoC] scala.implementation status
Posted by Simon Laws <si...@googlemail.com>.
Hi Guilherme
On Mon, Jun 13, 2011 at 4:02 PM, Guilherme Armigliatto
<gu...@gmail.com> 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