static final class NormProxy.ConstrainableNormProxy extends NormProxy implements RemoteMethodControl
NormProxy.ConstrainableNormProxy
Modifier and Type | Field and Description |
---|---|
private static long |
serialVersionUID |
server, uuid
Constructor and Description |
---|
NormProxy.ConstrainableNormProxy(NormServer server,
Uuid serverUuid)
Creates an instance of this class.
|
Modifier and Type | Method and Description |
---|---|
MethodConstraints |
getConstraints()
Returns the client constraints placed on this proxy.
|
private ProxyTrustIterator |
getProxyTrustIterator()
Returns a proxy trust iterator that yields this object's server.
|
private void |
readObject(ObjectInputStream in)
Require server to implement RemoteMethodControl.
|
RemoteMethodControl |
setConstraints(MethodConstraints constraints)
Returns a new copy of this proxy with the client constraints set to the
specified constraints.
|
create, createLeaseRenewalSet, getAdmin
equals, getReferentUuid, hashCode
private static final long serialVersionUID
NormProxy.ConstrainableNormProxy(NormServer server, Uuid serverUuid)
private void readObject(ObjectInputStream in) throws IOException, ClassNotFoundException
IOException
ClassNotFoundException
public RemoteMethodControl setConstraints(MethodConstraints constraints)
RemoteMethodControl
getConstraints
method of the copy returns
the identical constraints instance. The original proxy is not modified.
A null
value is interpreted as mapping all methods to
empty constraints (one that has no requirements and no preferences).
For any given remote call, the specific client requirements and
preferences to be satisfied are given by the return value of invoking
the getConstraints
method of
the specified MethodConstraints
instance with a
Method
object representing the remote method.
Client constraints placed on a proxy are included in the serialized
state of the proxy. This allows third-party services to be transparent
to the client's needs. For example, if remote object s1
obtains a proxy for remote object s2
, and passes that
proxy to remote object s3
, expecting s3
to
invoke a remote method on s2
, then s1
can
control that call by placing its constraints directly on the proxy
before passing it to s3
. If s3
does not
wish to be transparent in this way, then it should explicitly replace
the client constraints on received proxies with whatever constraints
are appropriate to implement its own policy.
setConstraints
in interface RemoteMethodControl
constraints
- client constraints, or null
RemoteMethodControl.getConstraints()
public MethodConstraints getConstraints()
RemoteMethodControl
null
, which is interpreted as mapping all
methods to empty constraints (one that has no requirements and no
preferences).getConstraints
in interface RemoteMethodControl
null
RemoteMethodControl.setConstraints(net.jini.core.constraint.MethodConstraints)
private ProxyTrustIterator getProxyTrustIterator()
Copyright 2007-2013, multiple authors.
Licensed under the Apache License, Version 2.0, see the NOTICE file for attributions.