Just to be clear, these are all *Akka* actors, right? Parts of your post make it sound as if some other Java actor library might be involed.
If it's just Akka actors written in Java, there's no problem creating Java actors in Scala and vice-versa. We have a mixed language codebase and that works just fine. On Friday, November 21, 2014 6:23:40 PM UTC-7, David wrote: > > Hello, > > I am being asked to leverage pre-existing actors in a Java lib but my > codebase is in pure Scala. > > These pre-existing actors provide some "aspect" functionality like metrics > and monitoring although I could implement my own. > > 1. Has anyone seen systems like this - is this a common design? > > I am just trying this out and find just creating those Java based actors, > say using the context of a Scala based actor is confusing. > Can I use a Scala Props to create a Java actor? > > I am not sure even what the stack traces look like for actor systems > comprised of both Scala and Java actors when failures happen. > > I know this is a general question but am looking for lessons learned in > case someone else was forced down a similar situation. > > Thanks > -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
