There is very nice example at typesafe templates, checkout this link
akka-persistence-event-sourcing
http://typesafe.com/activator/template/akka-persistence-event-sourcing
On Friday, April 3, 2015 at 8:53:50 PM UTC+3, Lukas Welte wrote:
Hi,
I'm trying to figure out how one would model a
Hi guys,
We have setup an Akka cluster in EC2 following the setup described here
http://chrisloy.net/2014/05/11/akka-cluster-ec2-autoscaling.html. The
main purpose is to use it for creating cluster singletons to perform a
number of batch tasks. We also use Websocket support in Play framework
Hi there,
if you mean the new akka-typed module then: no. It's currently an preview
which has not been released yet (it will be in 2.4),
this it does not yet have integration with peristence.
If you mean the old static interface typed actors then the answer is also
no.
These are only meant as an
First of all, you shouldn't ever block like this, as you do with Await.
As for your question - this sounds like something the parent actor should
be responsible for.
I'm not even sure the code above works (it at least never occurred to me to
try to create an actor using a full path as I always
Hi
Just want to consult if this make sense .
I have an actor that uses as a service to fetch data from the db .
for accessing the DB we have a Java Spring project with hibernate and Jpa
Repository
what is the best participate for testings :
the actor should receive as a parameter the
Hi Max,
3 apr 2015 kl. 13:25 skrev Maxymilian Śmiech
maxymilian.smi...@student.uw.edu.pl:
Hi,
I want to use ClusterSingletonManager, but it is not possible to set
supervision strategy for its child (like with Router). What should I do?
copy ClusterSingletonManager implementation and
Hi,
is there a way to create TypedActors which are persistent at the same time
in Akka?
Any examples will be very helpful.
Thanks
Explorer
--
Read the docs: http://akka.io/docs/
Check the FAQ:
http://doc.akka.io/docs/akka/current/additional/faq.html
Search the archives:
Hi,
I want to create an actor if it didn't created already. To check its
existence I use actorSelection. If there is no actor defined by the path, I
create a new one with actorOf.
Is this approach correct? How can I improve the design? Here is the code I
come up with currently;
val fullPath: