Hi Folks,
I have two 3rd party libraries I need to use in my application. Both use
Akka, but they use different versions (2.1 and 2.3, I think). Since I need
to use these versions together in the same JVM (I don't need 2.1 and 2.3 to
talk to each other, just share a VM), I started looking at lo
in for repairs) to divine why the classloader
> you supply to your ActorSystem creation does not have access to the
> akka-remote jar.
>
> Could you share that?
>
>
> On Fri, Apr 4, 2014 at 12:17 AM, Bryn Keller wrote:
>
>> Hi Folks,
>>
>> I have two
sLoader to be the appropriate
> one around the thing-block
> c) try to load the class Akka reports as missing from the ClassLoader
> you're using
>
> (You have entered the world of class loaders, a world of advice: Here be
> dragons)
>
>
>
> On Fri, Apr 4, 2014 at 12:5
Hi Folks,
We have an application that needs to run in an environment where it is not
allowed to listen on any new sockets. It can connect to remote servers, but
it can't be a server itself.
Is there any way to use Akka in that kind of environment to talk to an Akka
service on another machine?
Thanks, Endre.
I'm not quite clear on what you're saying - I understand Akka wants to work
in peer-to-peer mode, but I don't understand this part:
This does not mean that you cannot use Akka in a Client-Server setup
>> though, but you will need to implement your own client-server connection.
>> T
