JGDMS Project 3.0-SNAPSHOT API Documentation

Skip navigation links

Module :: JGDMS Jini Extensible Remote Invocation 3.0-SNAPSHOT API

Release Notes for net.jini.jeri net.jini.jeri
JGDMS v3.0.0 Release Notes Description The Description

Packages 
Package Description
net.jini.jeri
Provides the fundamental abstractions and standard implementation classes for Jini extensible remote invocation (Jini ERI).
net.jini.jeri.connection
Provides interfaces and classes for implementing connection-based Jini extensible remote invocation (Jini ERI) transport layer providers.
net.jini.jeri.http
Provides implementations of the Endpoint and ServerEndpoint abstractions that use HTTP messages sent over TCP sockets as the underlying communication mechanism.
net.jini.jeri.kerberos
Provides implementations of Endpoint and ServerEndpoint that use Kerberos as the underlying network security protocol to support security related invocation constraints for remote requests.
net.jini.jeri.ssl
Provides implementations of Endpoint and ServerEndpoint that use TLS/SSL and HTTPS (HTTP over TLS/SSL) to support invocation constraints.
net.jini.jeri.tcp
Provides implementations of the Endpoint and ServerEndpoint abstractions that use TCP sockets as the underlying communication mechanism.
org.apache.river.jeri.internal  
org.apache.river.jeri.internal.connection  
org.apache.river.jeri.internal.http  
org.apache.river.jeri.internal.mux  
org.apache.river.jeri.internal.runtime  
Release Notes for net.jini.jeri

net.jini.jeri
JGDMS v3.0.0 Release Notes

    Description

    The net.jini.jeri package and its subpackages provide APIs for Jini extensible remote invocation (Jini ERI) and several Jini ERI transport layer providers.

    Changes since the v2.2.0 release

  • [RIVER-397] - Mux.start() can block indefinitely
  • [RIVER-142] - concurrency problem in DGC lease expiration handling

    • Changes since the v2.1.1 release

  • [RIVER-22] - NPE in net.jini.jeri.tcp.TcpEndpoint$ConnectionImpl.checkConnectPermission
  • [RIVER-209] - NullPointerException in SslConnection.checkConnectPermission()
  • [RIVER-212] - use of "enum" as a variable name
  • [RIVER-229] - reduce number of Reaper threads created by ConnectionManager
  • [RIVER-230] - (mux) SelectionManager catch Error block assumes getMessage() returns non-null
  • [RIVER-240] - BasicInvocationDispatcher.dispatch could log more info for some exceptions
  • [RIVER-254] - request initiation can block on I/O for inapplicable connection

    • Changes since the v2.0.1 release

    Multihomed host support

    As recommended by RFC 1123, the transport endpoints now attempt connections to all the IP addresses that a given host name may resolve to, instead of just the first one.

    Trust verification restriction

    BasicJeriTrustVerifier has been changed to trust fewer dynamic proxies. In particular, in addition to implementing RemoteMethodControl, the dynamic proxy must now implement one or more well-formed remote interfaces (ones that extend Remote and for which all methods declare RemoteException or a superclass in their throws clause), and must not implement any other interfaces except TrustEquivalence.

    New BasicJeriTrustVerifier protected methods

    BasicJeriTrustVerifier has five new protected methods to allow for more convenient implementation of certain behaviors through subclassing:

    • hasTrustedProxyClass can be overridden by subclasses to control which dynamic proxy classes for Jini ERI proxies are considered locally trusted.
    • hasTrustedClassLoader can be overridden by subclasses to control the set of class loaders for which the class of a Jini ERI proxy, when defined by one of those loaders, is considered locally trusted.
    • isTrustedProxyInterface can be overridden by subclasses to control which dynamic proxy interfaces for Jini ERI proxies are considered locally trusted.
    • isTrustedInvocationHandler can be overridden by subclasses to support verification of invocation handlers that have a locally trusted class other than BasicInvocationHandler (such as a subclass of BasicInvocationHandler).
    • checkInvocationHandlerContent can be invoked by subclasses that override isTrustedInvocationHandler to perform the verification steps that the default implementation of isTrustedInvocationHandler would perform, except that the class of the invocation handler is not required to be BasicInvocationHandler exactly, so that trusted subclasses can be supported.
    Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
Skip navigation links
Copyright ©, multiple authors.
  • Prev
  • Next

Copyright © 2016–2018. All rights reserved.