New candidate JEP: 407: Remove RMI Activation

Peter Firmstone peter.firmstone at zeus.net.au
Sat May 1 02:27:58 UTC 2021


Can we retain the following API classes please, marked as deprecated, 
but not for removal?

We have our own implementation of Activation, that we register with the 
RMI Registry.

Removing these classes will cause many breakages and incompatibilities, 
we don't need the implementation of Activation.

Apache River also uses these and has it's own implementation of 
Activation called Phoenix.

The following interfaces:

java.rmi.activation.ActivationInstantiator;
java.rmi.activation.ActivationMonitor;
java.rmi.activation.ActivationSystem;
java.rmi.activation.Activator;

The following Exceptions:

java.rmi.activation.ActivateFailedException;
java.rmi.activation.ActivationException;
java.rmi.activation.UnknownObjectException;
java.rmi.activation.ActivationException;
java.rmi.activation.UnknownGroupException;

The following classes:

java.rmi.activation.ActivationID;
java.rmi.activation.ActivationGroupDesc;
java.rmi.activation.ActivationGroupDesc.CommandEnvironment;
java.rmi.activation.ActivationGroupID;
java.rmi.activation.ActivationDesc;

-- 
Regards,
  
Peter Firmstone
Zeus Project Services Pty Ltd.


On 27/03/2021 4:01 am, mark.reinhold at oracle.com wrote:
> https://openjdk.java.net/jeps/407
>
>    Summary: Remove the Remote Method Invocation (RMI) Activation
>    mechanism, while preserving the rest of RMI.
>
> - Mark



More information about the jdk-dev mailing list