Fabrizio,

Regarding the community, the akka-user list is much more welcoming, calm
user list than compared with scala-user. I can't say enough about the
quality of the team with guys like Roland, Viktor and Jonas leading the
community.

On Sat, Sep 29, 2012 at 10:53 PM, <[email protected]> wrote:

>   Today's Topic Summary
>
> Group: http://groups.google.com/group/javaposse/topics
>
>    - Testing Actors in Akka, the book <#13a15bc51696f445_group_thread_0>[6 
> Updates]
>
>   Testing Actors in Akka, the 
> book<http://groups.google.com/group/javaposse/t/1196538a27c0e6b1>
>
>    "Fabrizio Giudici" <[email protected]> Sep 29 08:24PM
>    +0200
>
>    Just seen the advertising by Manning of this book. Which would be
>    quite
>    interesting for me, but it seems that examples are only in Scala -
>    which
>    makes it useless for me. Is there any similar resource with examples
>    in
>    Java? I'm doing more experiments with actors and I'd like to see a
>    structured approach to testing, to compare what I've done so far.
>
>    --
>    Fabrizio Giudici - Java Architect, Project Manager
>    Tidalwave s.a.s. - "We make Java work. Everywhere."
>    [email protected]
>    http://tidalwave.it - http://fabriziogiudici.it
>
>
>
>
>    Kevin Wright <[email protected]> Sep 29 08:09PM +0100
>
>    Akka's own documentation is rather good, and free, and has dedicated
>    sections to cover all the relevant functionality via both the Scala and
>    Java APIs.
>
>    Having said that (and my opinion may be seen as controversial here)...
>    You
>    may find it easier to start learning the Scala API and then apply that
>    understanding to Java. Pattern matching and first-class functions are
>    both
>    very heavily used concepts and can be directly expressed in Scala,
>    once you
>    understand the "big picture" then Java's encoding of these ideas will
>    be
>    far less distracting from the core ideas.
>
>
>
>    On Sep 29, 2012 7:24 PM, "Fabrizio Giudici" <
>    [email protected]>
>    wrote:
>
>
>
>
>
>    "Fabrizio Giudici" <[email protected]> Sep 29 09:26PM
>    +0200
>
>    On Sat, 29 Sep 2012 21:09:16 +0200, Kevin Wright
>    > you
>    > understand the "big picture" then Java's encoding of these ideas
>    will be
>    > far less distracting from the core ideas.
>
>    I don't have problems with the Akka APIs (Java in my case), which I'm
>    already using - though still at an elementary level.
>    I'm searching for something specifically aimed at tests with agents.
>    For
>    instance, in my studies so far I've ended up with writing a small
>    message
>    recorder and the Hamcrest support for post-test assertions, as in some
>    tests I'm verifying that there's a specific exchange of messages. I
>    bet
>    this is naive, due to the async nature of ages. What I need are agent
>    testing best practices, I suppose there are some out there...
>
>
>    --
>    Fabrizio Giudici - Java Architect @ Tidalwave s.a.s.
>    "We make Java work. Everywhere."
>    http://tidalwave.it/fabrizio/blog - [email protected]
>
>
>
>
>    Ricky Clarkson <[email protected]> Sep 29 04:30PM -0300
>
>    I'd guess the ideas in the book work for Java and for Scala. I'm sure
>    the
>    akka community will help you port anything you struggle with.
>    On Sep 29, 2012 4:26 PM, "Fabrizio Giudici" <
>    [email protected]>
>    wrote:
>
>
>
>
>
>    "Fabrizio Giudici" <[email protected]> Sep 29 09:56PM
>    +0200
>
>    On Sat, 29 Sep 2012 21:30:50 +0200, Ricky Clarkson
>
>    > I'd guess the ideas in the book work for Java and for Scala.
>
>    Sure, they're just best practices. But I find Scala absolutely
>    unreadable
>    :o)
>
>
>    > I'm sure the akka community will help you port anything you struggle
>    > with.
>
>    ... and I'd like not to bother people with the unavoidable beginner
>    stuff
>    I'll deal with for some time.
>
>
>
>
>    --
>    Fabrizio Giudici - Java Architect @ Tidalwave s.a.s.
>    "We make Java work. Everywhere."
>    http://tidalwave.it/fabrizio/blog - [email protected]
>
>
>
>
>    Kevin Wright <[email protected]> Sep 29 10:21PM +0100
>
>    Talking about "exchange of messages", I'm assuming you mean actors and
>    not
>    agents (which are a distinct concept). The usual approach is to use a
>    `TestActorRef` which then forces everything to be
>    synchronous/deterministic
>    and gives you access to the guts of the underlying actor
>    implementation.
>
>    Doc for scala is here:
>    http://doc.akka.io/docs/akka/2.0.3/scala/testing.html
>    Surprisingly, this is one area where Akka doesn't provide an equivalent
>    page for Java. The ideas should be directly translatable to Java
>    though.
>
>
>    As for community, Akka's is perhaps the most friendly of any in the
>    Scala
>    ecosystem. Please don't hold back from asking even very-beginner-level
>    questions there. It might also be a good place to ask about
>    Java-oriented
>    documentation for the Akka test kit :)
>
>    Failing that... You can always ask on stack overflow, I've found it
>    generally has a very fast turnover rate for questions on Akka or
>    Scala, and
>    you'll leave the answer in a place where it can more easily be found
>    by the
>    next person to ask!
>
>
>
>    On 29 September 2012 20:26, Fabrizio Giudici
>
>    > "We make Java work. Everywhere."
>    > http://tidalwave.it/fabrizio/**blog <
>    http://tidalwave.it/fabrizio/blog> -
>    > [email protected]
>
>    --
>    Kevin Wright
>    mail: [email protected]
>    gtalk / msn : [email protected]
>    quora: http://www.quora.com/Kevin-Wright
>    google+: http://gplus.to/thecoda
>    <[email protected]>
>    twitter: @thecoda
>    vibe / skype: kev.lee.wright
>    steam: kev_lee_wright
>
>    "My point today is that, if we wish to count lines of code, we should
>    not
>    regard them as "lines produced" but as "lines spent": the current
>    conventional wisdom is so foolish as to book that count on the wrong
>    side
>    of the ledger" ~ Dijkstra
>
>
>
>  You received this message because you are subscribed to the Google Group
> javaposse.
> You can post via email <[email protected]>.
> To unsubscribe from this group, 
> send<[email protected]>an empty message.
> For more options, visit <http://groups.google.com/group/javaposse/topics>this 
> group.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Java Posse" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/javaposse?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups "Java 
Posse" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/javaposse?hl=en.

Reply via email to