N.B. I've added equivalent methods using MarshalledInstance in a backward compatible manner and deprecated uses of MarshalledObject in the api, with the exception of activation constructors, however, even in these cases, it's possible to convert MarshalledInstance to MarshalledObject and back again without ever invoking JRMP.
Regards, Peter. Sent from my Samsung device. Include original message ---- Original message ---- From: Peter Firmstone <peter.firmst...@zeus.net.au> Sent: 16/01/2017 10:16:41 am To: dev@river.apache.org <dev@river.apache.org> Subject: Extensible MarshalledInstance Reference: https://github.com/pfirmstone/river-internet/blob/trunk/src/net/jini/io/MarshalledInstance.java The River PMC is discouraging the use of JRMP RMI protocols, since the removal of support for JRMP in River 2.2.3. MarshalledObject utilises JRMP, so discouraging (deprecating) its use and providing MarshalledInstance equivalent methods throughout River's api makes a lot of sense. Since the community has also been discussing utilising other serialization protocols, I have created an extensible version of MarshalledInstance, at the above reference. Thoughts? Regards, Peter. Sent from my Samsung device.
