Hi Paul,
You raise a valid point about still using java serialization in some places
by default.
In general we strongly advertise against using the java serializer (slow,
and schema evolution hostile) - which again is the culprit here...
You're right however that it's one of our internal classes
Hi hAkkers,
ActorIdentity is serialized with java serializer (including its member
Option[]) and as such it cannot be successfully received across the nodes
with different Scala versions (2.10 vs 2.11). That presents 2 kinds of
problems for systems relying on it (including some cluster contrib
