net.jini.activation| Package | Description |
|---|---|
| net.jini.activation |
Extensions to the Java(TM) Remote Method Invocation (Java RMI) activation
framework to support activatable objects that are exported using an
Exporter to go inactive, to provide invocation
handlers for exporters that want to use dynamic proxies for
activatable remote objects, and to support trust verification of
secure activatable dynamic proxies and secure activation identifiers. |
net.jini.activationThe
net.jini.activation package provides extensions to the
Java(TM) Remote Method Invocation (Java RMI) activation framework.
ActivatableInvocationHandler by default no longer attempts
to propagate dynamic permission grants from the dynamic proxy to the
underlying activation identifier. If this functionality is required, it can
be enabled by setting the
org.apache.river.activation.enableActivateGrant system property to
true. If the
phoenix activator has been configured
to allow anonymous client activation requests, and the invocation
constraints on the underlying activation identifier have been configured
to allow anonymous activation calls, it is not necessary to enable this.
That should be the preferred configuration. However, if the activator has
been configured to use Kerberos authentication, then anonymous calls are
not supported, and you will either have to enable the activate grant in
clients and dynamically grant sufficient
AuthenticationPermission and
GrantPermission to the proxy to permit activation calls
to succeed, or else statically grant sufficient
AuthenticationPermission to downloaded code in clients
to permit activation calls to succeed.
Copyright © 2016–2018. All rights reserved.