/*
 * Copyright (c) 1998, 2018, Oracle and/or its affiliates. All rights reserved.
 * DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER.
 * <p>
 * This code is free software; you can redistribute it and/or modify it
 * under the terms of the GNU General Public License version 2 only, as
 * published by the Free Software Foundation.  Oracle designates this
 * particular file as subject to the "Classpath" exception as provided
 * by Oracle in the LICENSE file that accompanied this code.
 * <p>
 * This code is distributed in the hope that it will be useful, but WITHOUT
 * ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
 * FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public License
 * version 2 for more details (a copy is included in the LICENSE file that
 * accompanied this code).
 * <p>
 * You should have received a copy of the GNU General Public License version
 * 2 along with this work; if not, write to the Free Software Foundation,
 * Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA.
 * <p>
 * Please contact Oracle, 500 Oracle Parkway, Redwood Shores, CA 94065 USA
 * or visit www.oracle.com if you need additional information or have any
 * questions.
 */

Provides support for RMI Object Activation. A remote object's reference can be made ``persistent'' and later activated into a ``live'' object using the RMI activation mechanism.

Implementations are not required to support the activation mechanism. If activation is not supported by this implementation, several specific activation API methods are all required to throw UnsupportedOperationException. If activation is supported by this implementation, these methods must never throw UnsupportedOperationException. These methods are denoted by the presence of an entry for UnsupportedOperationException in the Throws section of each method's specification.

Since:1.2
/** * Provides support for RMI Object Activation. A remote * object's reference can be made ``persistent'' and later activated into a * ``live'' object using the RMI activation mechanism. * * <p>Implementations are not required to support the activation * mechanism. If activation is not supported by this implementation, * several specific activation API methods are all required to throw * {@code UnsupportedOperationException}. If activation is supported by this * implementation, these methods must never throw {@code * UnsupportedOperationException}. These methods are denoted by the * presence of an entry for {@code UnsupportedOperationException} in the * <strong>Throws</strong> section of each method's specification. * * @since 1.2 */
package java.rmi.activation;