--
You received this message because you are subscribed to the Google Groups "Vienna Scala Users' Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scala-vienna...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
- Dependency-Injection. How do you do DI in Scala? (spring? cake? subcut? guice? roll-your-own?)
--
You received this message because you are subscribed to the Google Groups "Vienna Scala Users' Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scala-vienna...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Yes, you may call me Master :D It's somewhere between confidential and too abstract to be described, so i'll give you more details when ... uh... i know what it is that I need to do :)
I got an approval for my first project in Scala today ( Yes, we can!!!!!) which will include loooooads of testing, so maybe i could put something together on 'Advance testing', maybe for the May meeting ( Once i become the testing master!).
On Friday, March 1, 2013 at 2:26 PM, Gerald Loeffler wrote:
hi,good topics all! Let me add two thoughts:- on the topic of DI: i'm always a bit surprised by how this is approached in the Scala world, and would be prepared to give a talk on Spring Scala and "what a Java developer expects of DI in Scala".
- on the topic of Akka: i find the comparison of Akka and EJBs (especially asynchronous Session bean methods) particularly interesting and enlightening, and would be willing to give a presentation exploring this theme, if others share that interest.
- on the topic of Akka: i find the comparison of Akka and EJBs (especially asynchronous Session bean methods) particularly interesting and enlightening, and would be willing to give a presentation exploring this theme, if others share that interest.I am also very interested in Akka but at a more fundamental level. It's still a bit of magic to me from a conceptual level and thus I would like to have a talk+discussion in one of our meetups about what Akka's approach brings to the table and why it is fundamentally (?) different to the current Threads-a-plenty + mutable-state a-go-go approach.To be honest, I still do not truly understand that.
More advanced Akka topics I would be interested in, are discussions around what the ActiveMQ project did with the Apollo re-write: http://activemq.apache.org/apollo/documentation/architecture.htmland under which conditions a similar approach would make sense for other open-source projects.
--
--
You received this message because you are subscribed to the Google Groups "Vienna Scala Users' Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scala-vienna...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--