Issues with using Kryo for needed speed in serialization/deserialization
This post has NOT been accepted by the mailing list yet.
Our enterprise application needs to batch very large numbers of log lines into a large (1G) mule message, which is taking too long to serialize/deserialize in a persisted vm:connector queue.
So we wanted to try Kryo instead of the Java serializer/deserializer. But Kryo needs a serializable class to have a zero-arg constructor and fails on DefaultMuleEvent because of that.
Is it possible to subclass and use our own DefaultMuleEvent (and probably also DefaultMuleMessage) class?
We could then add a zero-argument constructor in our subclass. We are aware of the registry-bootstrap.properties file, but don't believe we can register the new subclass so that mule uses our subclass instead.