Spec-Zone .ru спецификации, руководства, описания, API

Uses of Class
org.omg.CORBA.SystemException

Packages that use SystemException

javax.rmi.CORBA	Contains portability APIs for RMI-IIOP.
org.omg.CORBA	Provides the mapping of the OMG CORBA APIs to the JavaTM programming language, including the class ORB, which is implemented so that a programmer can use it as a fully-functional Object Request Broker (ORB).
org.omg.CORBA.portable	Provides a portability layer, that is, a set of ORB APIs that makes it possible for code generated by one vendor to run on another vendor's ORB.

Uses of SystemException in javax.rmi.CORBA

Methods in javax.rmi.CORBA with parameters of type SystemException

RemoteException	UtilDelegate.mapSystemException(SystemException ex) Delegation call for Util.mapSystemException(org.omg.CORBA.SystemException).
static RemoteException	Util.mapSystemException(SystemException ex) Maps a SystemException to a RemoteException.

Uses of SystemException in org.omg.CORBA

Subclasses of SystemException in org.omg.CORBA

class	ACTIVITY_COMPLETED The ACTIVITY_COMPLETED system exception may be raised on any method for which Activity context is accessed.
class	ACTIVITY_REQUIRED The ACTIVITY_REQUIRED system exception may be raised on any method for which an Activity context is required.
class	BAD_CONTEXT Exception thrown when an operation is invoked by a client but the passed context does not contain the context values required by the operation.
class	BAD_INV_ORDER This exception indicates that the caller has invoked operations in the wrong order.
class	BAD_OPERATION Exception thrown when an object reference denotes an existing object, but that the object does not support the operation that was invoked.
class	BAD_PARAM Exception thrown when a parameter passed to a call is out of range or otherwise considered illegal.
class	BAD_QOS The BAD_QOS exception is raised whenever an object cannot support the quality of service required by an invocation parameter that has a quality of service semantics associated with it.
class	BAD_TYPECODE Exception thrown when the ORB has encountered a malformed type code (for example, a type code with an invalid TCKind value).
class	CODESET_INCOMPATIBLE This exception is raised whenever meaningful communication is not possible between client and server native code sets.
class	COMM_FAILURE This exception is raised if communication is lost while an operation is in progress, after the request was sent by the client, but before the reply from the server has been returned to the client.
class	DATA_CONVERSION This exception is raised if an ORB cannot convert the representation of data as marshaled into its native representation or vice-versa.
class	FREE_MEM Exception thrown when the ORB failed in an attempt to free dynamic memory, for example because of heap corruption or memory segments being locked.
class	IMP_LIMIT This exception indicates that an implementation limit was exceeded in the ORB run time.
class	INITIALIZE Exception thrown when an ORB has encountered a failure during its initialization, such as failure to acquire networking resources or detecting a configuration error.
class	INTERNAL This exception indicates an internal failure in an ORB, for example, if an ORB has detected corruption of its internal data structures.
class	INTF_REPOS Exception raised when an ORB cannot reach the interface repository, or some other failure relating to the interface repository is detected.
class	INV_FLAG Exception thrown when an invalid flag was passed to an operation (for example, when creating a DII request).
class	INV_IDENT This exception indicates that an IDL identifier is syntactically invalid.
class	INV_OBJREF This exception indicates that an object reference is internally malformed.
class	INV_POLICY Standard exception thrown when an invocation cannot be made because of an incompatibility between Policy overrides that apply to the particular invocation.
class	INVALID_ACTIVITY The INVALID_ACTIVITY system exception may be raised on the Activity or Transaction services' resume methods if a transaction or Activity is resumed in a context different to that from which it was suspended.
class	INVALID_TRANSACTION Exception thrown when the request carried an invalid transaction context.
class	MARSHAL A request or reply from the network is structurally invalid.
class	NO_IMPLEMENT This exception indicates that even though the operation that was invoked exists (it has an IDL definition), no implementation for that operation exists.
class	NO_MEMORY Exception thrown when the ORB run time has run out of memory.
class	NO_PERMISSION Exception thrown when an invocation failed because the caller has insufficient privileges.
class	NO_RESOURCES Exception thrown when the ORB has encountered some general resource limitation.
class	NO_RESPONSE This exception is raised if a client attempts to retrieve the result of a deferred synchronous call, but the response for the request is not yet available.
class	OBJ_ADAPTER This exception typically indicates an administrative mismatch, for example, a server may have made an attempt to register itself with an implementation repository under a name that is already in use, or is unknown to the repository.
class	OBJECT_NOT_EXIST Exception raised whenever an invocation on a deleted object was performed.
class	PERSIST_STORE This exception indicates a persistent storage failure, for example, failure to establish a database connection or corruption of a database.
class	REBIND REBIND is raised when the current effective RebindPolicy, has a value of NO_REBIND or NO_RECONNECT and an invocation on a bound object reference results in a LocateReply message with status OBJECT_FORWARD or a Reply message with status LOCATION_FORWARD.
class	TIMEOUT TIMEOUT is raised when no delivery has been made and the specified time-to-live period has been exceeded.
class	TRANSACTION_MODE The CORBA TRANSACTION_MODE exception is thrown by the client ORB if it detects a mismatch between the InvocationPolicy in the IOR and the chosen invocation path (i.e, direct or routed invocation).
class	TRANSACTION_REQUIRED Exception indicates that the request carried a null transaction context, but an active transaction is required.
class	TRANSACTION_ROLLEDBACK Exception thrown when the transaction associated with the request has already been rolled back or marked to roll back.
class	TRANSACTION_UNAVAILABLE The CORBA TRANSACTION_UNAVAILABLE exception is thrown by the ORB when it cannot process a transaction service context because its connection to the Transaction Service has been abnormally terminated.
class	TRANSIENT Exception thrown when the ORB attempted to reach an object and failed.
class	UNKNOWN This exception is raised if an operation implementation throws a non-CORBA exception (such as an exception specific to the implementation's programming language), or if an operation raises a user exception that does not appear in the operation's raises expression.

Uses of SystemException in org.omg.CORBA.portable

Subclasses of SystemException in org.omg.CORBA.portable

class	IndirectionException The Indirection exception is a Java specific system exception.
class	UnknownException The org.omg.CORBA.portable.UnknownException is used for reporting unknown exceptions between ties and ORBs and between ORBs and stubs.

Methods in org.omg.CORBA.portable that throw SystemException

OutputStream

InvokeHandler._invoke(String method, InputStream input, ResponseHandler handler) Invoked by the ORB to dispatch a request to the servant.