org.omg.CORBA Documentation Differences

This file contains all the changes in documentation in the package org.omg.CORBA as colored differences. Deletions are shown like this, and additions are shown like this.

If no deletions or additions are shown in an entry, the HTML tags will be what has changed. The new HTML tags are shown in the differences. If no documentation existed, and then some was added in a later version, this change is noted in the appropriate class pages of differences, but the change is not shown on this page. Only changes in existing text are shown here. Similarly, documentation which was inherited from another class or interface is not shown here.

Note that an HTML error in the new documentation may cause the display of other documentation changes to be presented incorrectly. For instance, failure to close a <code> tag will cause all subsequent paragraphs to be displayed differently.

Extracts the Principal object in this Any object's value field. Note that the class Principal has been deprecated. @return the Principal object stored in this Any object @exception BAD_OPERATION if this Any object contains something other than a Principal object or the value field has not yet been set @see CORBA package comments for unimplemented features @deprecated Deprecated by CORBA 2.2.

Extracts the java.math.BigDecimal object in this Any object's value field. @return the java.math.BigDecimal object stored in this Any object @exception BAD_OPERATION if this Any object contains something other than a java.math.BigDecimal object or the value field has not yet been set @see CORBA package comments for unimplemented features

Inserts the given Principal object into this Any object's value field. Note that the class Principal has been deprecated. @param p the Principal object to insert into this Any object @see CORBA package comments for unimplemented features @deprecated Deprecated by CORBA 2.2.

Inserts the given Streamable object into this Any object's value field. This method allows the insertion of non-primitive IDL types. @param s the Streamable object to insert into this Any object; may be a non-primitive IDL type @see CORBA package comments for unimplemented features

Throws an org.omg.CORBA.NO_IMPLEMENT exception.

Inserts the given java.math.BigDecimal object into this Any object's value field. @param value the java.math.BigDecimal object to insert into this Any object @param type the TypeCode object that is to be inserted into this Any object's type field and that describes the java.math.BigDecimal object being inserted @throws org.omg.CORBA.BAD_INV_ORDER if this method is invoked improperly @see CORBA package comments for unimplemented features

Writes out the value of this Any object to the given output stream. theIf both typecode and value ofneed thisto be written use Anycreate_output_stream() objectto create an OutputStream then use write_any on the OutputStream.

If this method is called on an Any object that has not had a value inserted into its value field it will throw the exception java.lang.NullPointerException. @param os the org.omg.CORBA.portable.OutputStream object into which to marshal the value and typecode of this Any object

The Holder for Any. For more information on Holder files see "Generated Files: Holder Files".

A Holder class for Any objects that is used to store "out" and "inout" parameters in IDL methods. If an IDL method signature has an IDL any as an "out" or "inout" parameter the programmer must pass an instance of AnyHolder as the corresponding parameter in the method invocation; for "inout" parameters the programmer must also fill the "in" value to be sent to the server. Before the method invocation returns the ORB will fill in the value corresponding to the "out" value returned from the server.

If myAnyHolder is an instance of AnyHolder the value stored in its value field can be accessed with myAnyHolder.value. @version 1.14 09/09/97 @since JDK1.2

The Helper for AnySeq. For more information on Helper files see "Generated Files: Helper Files".

org/omg/CORBA/AnySeqHelper.java Generated by the IDL-to-Java compiler (portable) version "3.0" from streams.idl 13 May 1999 22:41:36 o'clock GMT+00:00 The class definition has been modified to conform to the following OMG specifications :

• ORB core as defined by CORBA 2.3.1 (formal/99-10-07)
• IDL/Java Language Mapping as defined in ptc/00-01-08

The Holder for AnySeq. For more information on Holder files see "Generated Files: Holder Files".

org/omg/CORBA/AnySeqHolder.java Generated by the IDL-to-Java compiler (portable) version "3.0" from streams.idl 13 May 1999 22:41:36 o'clock GMT+00:00

The CORBAException thrown BAD_CONTEXTwhen exception whichan operation is throwninvoked when there is an error processingby a client but the passed acontext does not contain the context objectvalues required by the operation.

It contains a minor code which gives more detailed information about what caused the exception and a completion status. It may also contain a string describing the exception. @see documentation on Java IDL exceptions @version 1.17 09/09/97 @since JDK1.2

TheThis CORBA BAD_INV_ORDER exception whichindicates that is thrown when methods are called out ofthe caller has invoked operations in the wrong order. For example it can be raised by an ORB if an application makes an ORB-related call without having correctly initialized the ORB first.

It contains a minor code which gives more detailed information about what caused the exception and a completion status. It may also contain a string describing the exception. @see documentation on Java IDL exceptions @version 1.18 09/09/97 @since JDK1.2

The CORBAException thrown BAD_OPERATIONwhen exception which is thrown whenan object reference denotes an aexisting object but that the object does not support the operation method is invalidthat was invoked.

It contains a minor code which gives more detailed information about what caused the exception and a completion status. It may also contain a string describing the exception. @see documentation on Java IDL exceptions @version 1.17 09/09/97 @since JDK1.2

The CORBAException thrown BAD_PARAMwhen exceptiona whichparameter passed to a call is thrown when an invalid parameter isout of range or otherwise considered illegal. An ORB may raise this exception if null values or null pointers are passed to an operation (for language mappings where the concept of a null pointers or null values applies). BAD_PARAM can also be raised as a result of a methodclient generating requests with incorrect parameters using the DII.

It contains a minor code which gives more detailed information about what caused the exception and a completion status. It may also contain a string describing the exception. @see documentation on Java IDL exceptions @see meaning of minor codes @version 1.18 09/09/97 @since JDK1.2

BAD_POLICYA isPolicyErrorCode one of the PolicyErrorCodes which would be filled in the PolicyError exception. @author rip-dev @version 1.7 0211 12/0203/0001

BAD_POLICY_TYPEA isPolicyErrorCode one of the PolicyErrorCodes which would be filled in the PolicyError exception. @author rip-dev @version 1.7 0211 12/0203/0001

Contains the value used to indicate a policy value that is incorrect for a valid policy type in a call to the create_policy method defined in the ORB class. @version 1.7 0210 12/0203/0001

The CORBAException thrown BAD_TYPECODEwhen exception which is thrown whenthe ORB has encountered a themalformed type specifiedcode (for example a typecodetype iscode with an invalid TCKind value).

It contains a minor code which gives more detailed information about what caused the exception and a completion status. It may also contain a string describing the exception. @see documentation on Java IDL exceptions @version 1.17 09/09/97 @since JDK1.2

The Holder for Boolean. For more information on Holder files see "Generated Files: Holder Files".

A Holder class for a boolean that is used to store "out" and "inout" parameters in IDL methods. If an IDL method signature has an IDL boolean as an "out" or "inout" parameter the programmer must pass an instance of BooleanHolder as the corresponding parameter in the method invocation; for "inout" parameters the programmer must also fill the "in" value to be sent to the server. Before the method invocation returns the ORB will fill in the value corresponding to the "out" value returned from the server.

If myBooleanHolder is an instance of BooleanHolder the value stored in its value field can be accessed with myBooleanHolder.value. @version 1.14 09/09/97 @since JDK1.2

The Helper for BooleanSeq. For more information on Helper files see "Generated Files: Helper Files".

org/omg/CORBA/BooleanSeqHelper.java Generated by the IDL-to-Java compiler (portable) version "3.0" from streams.idl 13 May 1999 22:41:36 o'clock GMT+00:00 The class definition has been modified to conform to the following OMG specifications :

• ORB core as defined by CORBA 2.3.1 (formal/99-10-07)
• IDL/Java Language Mapping as defined in ptc/00-01-08

The Holder for BooleanSeq. For more information on Holder files see "Generated Files: Holder Files".

org/omg/CORBA/BooleanSeqHolder.java Generated by the IDL-to-Java compiler (portable) version "3.0" from streams.idl 13 May 1999 22:41:36 o'clock GMT+00:00

A user exception thrown when a parameter is not within the legal bounds for the object that a method is trying to access. @see documentation on Java IDL exceptions

The Holder for Byte. For more information on Holder files see "Generated Files: Holder Files".

A Holder class for a byte that is used to store "out" and "inout" parameters in IDL methods. If an IDL method signature has an IDL octet as an "out" or "inout" parameter the programmer must pass an instance of ByteHolder as the corresponding parameter in the method invocation; for "inout" parameters the programmer must also fill the "in" value to be sent to the server. Before the method invocation returns the ORB will fill in the value corresponding to the "out" value returned from the server.

If myByteHolder is an instance of ByteHolder the value stored in its value field can be accessed with myByteHolder.value. @version 1.14 09/09/97 @since JDK1.2

The CORBAThis exception COMM_FAILUREis exceptionraised whichif communication is thrownlost while when therean operation is ain communicationprogress after the request was sent by the failureclient but before the reply from the server has been returned to the client.

It contains a minor code which gives more detailed information about what caused the exception and a completion status. It may also contain a string describing the exception.

See the section meaning of minor codes to see the minor codes for this exception. @see meaning of minor codes @version 1.17 09/09/97 @since JDK1.2

The Holder for Char. For more information on Holder files see "Generated Files: Holder Files".

A Holder class for a char that is used to store "out" and "inout" parameters in IDL methods. If an IDL method signature has an IDL char as an "out" or "inout" parameter the programmer must pass an instance of CharHolder as the corresponding parameter in the method invocation; for "inout" parameters the programmer must also fill the "in" value to be sent to the server. Before the method invocation returns the ORB will fill in the value corresponding to the "out" value returned from the server.

If myCharHolder is an instance of CharHolder the value stored in its value field can be accessed with myCharHolder.value. @version 1.14 09/09/97 @since JDK1.2

The Helper for CharSeq. For more information on Helper files see "Generated Files: Helper Files".

org/omg/CORBA/CharSeqHelper.java Generated by the IDL-to-Java compiler (portable) version "3.0" from streams.idl 13 May 1999 22:41:36 o'clock GMT+00:00 The class definition has been modified to conform to the following OMG specifications :

• ORB core as defined by CORBA 2.3.1 (formal/99-10-07)
• IDL/Java Language Mapping as defined in ptc/00-01-08

The Holder for CharSeq. For more information on Holder files see "Generated Files: Holder Files".

org/omg/CORBA/CharSeqHolder.java Generated by the IDL-to-Java compiler (portable) version "3.0" from streams.idl 13 May 1999 22:41:36 o'clock GMT+00:00

The Helper for CompletionStatus. For more information on Helper files see "Generated Files: Helper Files".

org/omg/CORBA/CompletionStatusHelper.java Generated by the IDL-to-Java compiler (portable) version "3.0" 03 June 1999 11:52:03 o'clock GMT+00:00

Retrieves the NamedValue objects whose name field matches the given name or name pattern. This method allows for wildcard searches which means that there can be multiple matches and therefore multiple values returned. If the property is not found at the indicated level the search continues up the context object tree until a match is found or all Context objects in the chain have been exhausted.

If no match is found an error is returned and no property list is returned. @param start_scope a String object indicating the context object level at which to initiate the search for the specified properties (for example "_USER" "_GROUP" "_SYSTEM"). Valid scope names are implementation-specific. If a scope name is omitted the search begins with the specified context object. If the specified scope name is not found an exception is returned. @param op_flags an operation flag. The one flag that may be specified is CTX_RESTRICT_SCOPE. If this flag is specified searching is limited to the specified start_scope or this Context object. @param pattern the property name whose values are to be retrieved. pattern may be a name or a name with a trailing wildcard character ("*"). @return an NVList containing all the property values (in the form of NamedValue objects) whose associated property name matches the given name or name pattern @see #set_values @see org.omg.CORBA.NamedValue

I Sets one or more property values in this Context object. The NVList supplied to this method contains one or more NamedValue objects. In each NamedValue object the name field holds the name of the property and the flags field must be set to zero. The NamedValue object's value field contains an Any object which in turn contains the value for the property. Since the value is always a string the Any object must have the kind field of its TypeCode set to TCKind.tk_string. @param values an NVList containing the property names and associated values to be set @see #get_values @see org.omg.CORBA.NamedValue @see org.omg.CORBA.Any

Interfaces derived from the Current interface enable ORB and CORBA services to provide access to information (context) associated with the thread of execution in which they are running. This information is accessed in a structured manner using interfaces derived from the Current interface defined in the CORBA module.

Each ORB or CORBA service that needs its own context derives an interface from the CORBA module's Current. Users of the service can obtain an instance of the appropriate Current interface by invoking ORB::resolve_initial_references.

org/omg/CORBA/Current.java Generated by the IDL-to-Java compiler (portable) version "3.0" from ../../../../../src/share/classes/org/omg/PortableServer/corba.idl Saturday July 17 1999 12:26:21 AM PDT.

The Helper for Current. For more information on Helper files see "Generated Files: Helper Files".

org/omg/CORBA/CurrentHelper.java Generated by the IDL-to-Java compiler (portable) version "3.0" from ../../../../../src/share/classes/org/omg/PortableServer/corba.idl Saturday July 17 1999 12:26:21 AM PDT

The Holder for Current. For more information on Holder files see "Generated Files: Holder Files".

org/omg/CORBA/CurrentHolder.java Generated by the IDL-to-Java compiler (portable) version "3.0" from ../../../../../src/share/classes/org/omg/PortableServer/corba.idl Saturday July 17 1999 12:26:21 AM PDT

The interface for Current. For more information on Operations interfaces see "Generated Files". org/omg/CORBA/CurrentOperations.java Generated by the IDL-to-Java compiler (portable) version "3.0" from ../../../../../src/share/classes/org/omg/PortableServer/corba.idl Saturday July 17 1999 12:26:21 AM PDT.

The CustomMarshal is anAn abstract value type that is meant to be used by the ORB not the user. Semantically it is treated as a custom valuetype's implicit base class although the custom valutype does not actually inherit it in IDL. The implementer of a custom value type shall provide an implementation of the CustomMarshal operations. The manner in which this is done is specified in the IDL to Java langague mapping. Each custom marshaled value type shall have its own implementation. @see DataOuputStream @see DataInputStream

TheThis CORBAexception is raised if an ORB cannot convert the representation of data as marshaled into its native representation or vice-versa. For example DATA_CONVERSION exception which is thrown when there is a data conversioncan be raised if wide character codeset conversion fails or errorif an ORB cannot convert floating point values between different representations.

It contains a minor code which gives more detailed information about what caused the exception and a completion status. It may also contain a string describing the exception.

See the section meaning of minor codes to see the minor codes for this exception. @see documentation on Java IDL exceptions @version 1.16 09/09/97 @since JDK1.2

Defines the methods used to read primitive data types from input streams for unmarshaling custom value types. This interface is used by user written custom unmarshaling code for custom value types. @see org.omg.CORBA.DataOutputStream @see org.omg.CORBA.CustomMarshal @version 1.6 028 12/0203/0001

Defines the methods used to write primitive data types to output streams for marshalling custom value types. This interface is used by user written custom marshalling code for custom value types. @see org.omg.CORBA.DataInputStream @see org.omg.CORBA.CustomMarshal @version 1.8 0210 12/0203/0001

The Helper for DefinitionKind. For more information on Helper files see "Generated Files: Helper Files".

org/omg/CORBA/DefinitionKindHelper.java Generated by the IDL-to-Java compiler (portable) version "3.0" from ir.idl 03 June 1999 11:33:43 o'clock GMT+00:00

Provides mechanisms for establishing and navigating relationships to superior and subordinate domains as well as for creating and accessing policies. The DomainManager has associated with it the policy objects for a particular domain. The domain manager also records the membership of the domain and provides the means to add and remove members. The domain manager is itself a member of a domain possibly the domain it manages. The domain manager provides mechanisms for establishing and navigating relationships to superior and subordinate domains and creating and accessing policies.

Provides the DomainManager with the means to access policies.

The DomainManager has associated with it the policy objects for a particular domain. The domain manager also records the membership of the domain and provides the means to add and remove members. The domain manager is itself a member of a domain possibly the domain it manages. The domain manager provides mechanisms for establishing and navigating relationships to superior and subordinate domains and creating and accessing policies.

This returns the policy of the specified type for objects in this domain. The types of policies available are domain specific. See the CORBA specification for a list of standard ORB policies. @param policy_type Type of policy to request

The Holder for Double. For more information on Holder files see "Generated Files: Holder Files".

A Holder class for a double that is used to store "out" and "inout" parameters in IDL methods. If an IDL method signature has an IDL double as an "out" or "inout" parameter the programmer must pass an instance of DoubleHolder as the corresponding parameter in the method invocation; for "inout" parameters the programmer must also fill the "in" value to be sent to the server. Before the method invocation returns the ORB will fill in the value corresponding to the "out" value returned from the server.

If myDoubleHolder is an instance of DoubleHolder the value stored in its value field can be accessed with myDoubleHolder.value. @version 1.14 09/09/97 @since JDK1.2

The Helper for DoubleSeq. For more information on Helper files see "Generated Files: Helper Files".

org/omg/CORBA/DoubleSeqHelper.java Generated by the IDL-to-Java compiler (portable) version "3.0" from streams.idl 13 May 1999 22:41:37 o'clock GMT+00:00 The class definition has been modified to conform to the following OMG specifications :

• ORB core as defined by CORBA 2.3.1 (formal/99-10-07)
• IDL/Java Language Mapping as defined in ptc/00-01-08

The Holder for DoubleSeq. For more information on Holder files see "Generated Files: Holder Files".

org/omg/CORBA/DoubleSeqHolder.java Generated by the IDL-to-Java compiler (portable) version "3.0" from streams.idl 13 May 1999 22:41:37 o'clock GMT+00:00

Enables org.omg.CORBA.Any values canto be dynamically interpreted (traversed) and constructed through DynAny objects. A DynAny object is associated with a data value which may correspond to a copy of the value inserted into an Any. The DynAny APIs enable traversal of the data value associated with an Any at runtime and extraction of the primitive constituents of the data value.

TheRepresents DynArray interface represents a DynAny object which is associated with an array.

TheRepresents DynEnum interface represents a DynAny object which is associated with an IDL enum.

The base class for all object implementations using the DSI. It defines a single abstract method invoke that a dynamic servant needs to implement. DynamicImplementation has been deprecated by the OMG in favor of the Portable Object Adapter. @version 1.6 09/09/97 @seedeprecated org.omg.CORBA.ServerRequest @since JDK1.2DynamicImplementation

Accepts a ServerRequest object and uses its methods to determine the request target operation and parameters and to set the result or exception.@deprecated Deprecated by the Portable Object Adapter. @param request a ServerRequest object representing the request to be invoked

TheException CORBA FREE_MEM exception which is thrown when the systemORB failed in is unablean attempt to free dynamic memory for example because of heap corruption or memory segments being locked.

It contains a minor code which gives more detailed information about what caused the exception and a completion status. It may also contain a string describing the exception. @see documentation on Java IDL exceptions @version 1.16 09/09/97 @since JDK1.2

The Helper for FieldName. For more information on Helper files see "Generated Files: Helper Files".

org/omg/CORBA/FieldNameHelper.java Generated by the IDL-to-Java compiler (portable) version "3.0" 03 June 1999 11:52:03 o'clock GMT+00:00

The Holder for Fixed. For more information on Holder files see "Generated Files: Holder Files".

FixedHolder is a container class for values of IDL type "fixed" which is mapped to the Java class java.math.BigDecimal. It is usually used to store "out" and "inout" IDL method parameters. If an IDL method signature has a fixed as an "out" or "inout" parameter the programmer must pass an instance of FixedHolder as the corresponding parameter in the method invocation; for "inout" parameters the programmer must also fill the "in" value to be sent to the server. Before the method invocation returns the ORB will fill in the contained value corresponding to the "out" value returned from the server. @version 1.14 09/09/97

The Holder for Float. For more information on Holder files see "Generated Files: Holder Files".

A Holder class for a float that is used to store "out" and "inout" parameters in IDL methods. If an IDL method signature has an IDL float as an "out" or "inout" parameter the programmer must pass an instance of FloatHolder as the corresponding parameter in the method invocation; for "inout" parameters the programmer must also fill the "in" value to be sent to the server. Before the method invocation returns the ORB will fill in the value corresponding to the "out" value returned from the server.

If myFloatHolder is an instance of FloatHolder the value stored in its value field can be accessed with myFloatHolder.value. @version 1.14 09/09/97 @since JDK1.2

The Helper for FloatSeq. For more information on Helper files see "Generated Files: Helper Files".

org/omg/CORBA/FloatSeqHelper.java Generated by the IDL-to-Java compiler (portable) version "3.0" from streams.idl 13 May 1999 22:41:37 o'clock GMT+00:00 The class definition has been modified to conform to the following OMG specifications :

• ORB core as defined by CORBA 2.3.1 (formal/99-10-07)
• IDL/Java Language Mapping as defined in ptc/00-01-08

The Holder for FloatSeq. For more information on Holder files see "Generated Files: Holder Files".

org/omg/CORBA/FloatSeqHolder.java Generated by the IDL-to-Java compiler (portable) version "3.0" from streams.idl 13 May 1999 22:41:37 o'clock GMT+00:00

The Helper for IDLType. For more information on Helper files see "Generated Files: Helper Files".

org/omg/CORBA/IDLTypeHelper.java Generated by the IDL-to-Java compiler (portable) version "3.0" from ir.idl 03 June 1999 11:33:44 o'clock GMT+00:00

The CORBAThis exception IMP_LIMITindicates exceptionthat whichan implementation islimit was thrown whenexceeded in the implementationORB limitrun time. For example an ORB may reach the maximum number of references it can hold simultaneously in an address space the size of a parameter may have exceeded the allowed maximum or an ORB may impose a maximum on the number of clients or servers that has been violatedcan run simultaneously.

It contains a minor code which gives more detailed information about what caused the exception and a completion status. It may also contain a string describing the exception. @see documentation on Java IDL exceptions @version 1.16 09/09/97 @since JDK1.2

TheException CORBA INITIALIZEthrown exception which is thrown when there is an ORBwhen an ORB has encountered a failure during its initialization such as failure to acquire networking resources or detecting a configuration error.

It contains a minor code which gives more detailed information about what caused the exception and a completion status. It may also contain a string describing the exception. @see documentation on Java IDL exceptions @version 1.19 09/09/97 @since JDK1.2

The CORBAThis exception INTERNALindicates exception which isan internal failure thrownin an ORB when there isfor example if an ORB has detected corruption of its internal errordata structures.

It contains a minor code which gives more detailed information about what caused the exception and a completion status. It may also contain a string describing the exception.

See the section meaning of minor codes to see the minor codes for this exception. @see documentation on Java IDL exceptions @version 1.16 09/09/97 @since JDK1.2

Constructs an INTERNAL exception with a default minor code of 0 and a completion state of COMPLETED_MAYBENO.

The CORBAException raised INTF_REPOSwhen exception which is thrown when there isan ORB cannot reach the interface repository anor some other error accessingfailure relating to the interface repository is detected.

It contains a minor code which gives more detailed information about what caused the exception and a completion status. It may also contain a string describing the exception. @see documentation on Java IDL exceptions @version 1.16 09/09/97 @since JDK1.2

TheException CORBAthrown when the request carried an invalid transaction context. INVALID_TRANSACTIONFor example this exception which iscould be thrownraised if an error occurred when there is a transaction errortrying to register a resource.

It contains a minor code which gives more detailed information about what caused the exception and a completion status. It may also contain a string describing the exception. @see documentation on Java IDL exceptions @version 1.5 09/09/97 @since JDK1.2

Constructs an INVALID_TRANSACTION exception with a default minor code of 0 and a completion state of COMPLETED_MAYBENO.

The CORBAException thrown INV_FLAGwhen exception which is thrown whenan invalid flag was passed to an invalidoperation flag(for example when creating a isDII specifiedrequest).

It contains a minor code which gives more detailed information about what caused the exception and a completion status. It may also contain a string describing the exception. @see documentation on Java IDL exceptions @version 1.16 09/09/97 @since JDK1.2

The CORBAThis exception INV_IDENTindicates exceptionthat whichan IDL identifier is thrownsyntactically invalid. It may be raised if for example an identifier passed to the interface repository whendoes not conform to IDL identifier syntax or if an illegal operation name is invalidused with the DII.

It contains a minor code which gives more detailed information about what caused the exception and a completion status. It may also contain a string describing the exception. @see documentation on Java IDL exceptions @version 1.16 09/09/97 @since JDK1.2

The CORBAThis exception INV_OBJREFindicates exceptionthat whichan object reference is throwninternally whenmalformed. anFor example the repository ID may have incorrect syntax or the addressing information may be invalid. This exception is raised by ORB::string_to_object referenceif the passed string does not decode correctly. An ORB may choose to detect calls via nil references (but is not obliged to do detect them). INV_OBJREF is specifiedused to indicate this.

It contains a minor code which gives more detailed information about what caused the exception and a completion status. It may also contain a string describing the exception.

See the section Minor Code Meanings to see the minor codes for this exception. @see documentation on Java IDL exceptions @version 1.17 09/09/97 @since JDK1.2

Constructs an INV_OBJREF exception with a default minor code of 0 and a completion state of COMPLETED_MAYBENO.

TheStandard CORBA INV_POLICY standard exception which is thrown when an invocation cannot be made because of an incompatibility between Policy overrides that apply to the particular invocation. It contains a minor code which gives more detailed information about what caused the exception and a completion status. It may also contain a string describing the exception. @see documentation on Java IDL exceptions @version 1.5 09/09/97

This is the Operations interface for the mapping from IRObject. Several interfaces are used as base interfaces for objects in the Interface Repository (IR). These base interfaces are not instantiable. A common set of operations is used to locate objects within the Interface Repository. Some of these operations are defined in the IRObject. All IR objects inherit from the IRObject interface which provides an operation for identifying the actual type of the object. (The IDL base interface IRObject represents the most generic interface from which all other Interface Repository interfaces are derived even the Repository itself.) All java implementations of IR objects must implement the IRObjectOperations interface. @see IDLTypeOperations @see IDLType @see IRObject

Destroys this object. If the object is a Container this method is applied to all its contents. If the object contains an IDLType attribute for an anonymous type that IDLType is destroyed. If the object is currently contained in some other object it is removed. If the method is invoked on a Repository or on a PrimitiveDef then the BAD_INV_ORDER exception is raised with minor value 2. An attempt to destroy an object that would leave the repository in an incoherent state causes BAD_INV_ORDER exception to be raised with the minor code 1. @exception BAD_INV_ORDER if this method is invoked on a repository or PrimitiveDef or if an attempt to destroy an object would leave the repository in an incoherent state

The Helper for Identifier. For more information on Helper files see "Generated Files: Helper Files".

org/omg/CORBA/IdentifierHelper.java Generated by the IDL-to-Java compiler (portable) version "3.0" from ir.idl 03 June 1999 11:33:42 o'clock GMT+00:00

The Holder for Int. For more information on Holder files see "Generated Files: Holder Files".

A Holder class for an int that is used to store "out" and "inout" parameters in IDL methods. If an IDL method signature has an IDL long as an "out" or "inout" parameter the programmer must pass an instance of IntHolder as the corresponding parameter in the method invocation; for "inout" parameters the programmer must also fill the "in" value to be sent to the server. Before the method invocation returns the ORB will fill in the value corresponding to the "out" value returned from the server.

If myIntHolder is an instance of IntHolder the value stored in its value field can be accessed with myIntHolder.value. @version 1.14 09/09/97 @since JDK1.2

The Holder for Long. For more information on Holder files see "Generated Files: Holder Files".

A Holder class for a long that is used to store "out" and "inout" parameters in IDL methods. If an IDL method signature has an IDL long long as an "out" or "inout" parameter the programmer must pass an instance of LongHolder as the corresponding parameter in the method invocation; for "inout" parameters the programmer must also fill the "in" value to be sent to the server. Before the method invocation returns the ORB will fill in the value corresponding to the "out" value returned from the server.

If myLongHolder is an instance of LongHolder the value stored in its value field can be accessed with myLongHolder.value. @version 1.14 09/09/97 @since JDK1.2

The Helper for LongLongSeq. For more information on Helper files see "Generated Files: Helper Files".

org/omg/CORBA/LongLongSeqHelper.java Generated by the IDL-to-Java compiler (portable) version "3.0" from streams.idl 13 May 1999 22:41:37 o'clock GMT+00:00 The class definition has been modified to conform to the following OMG specifications :

• ORB core as defined by CORBA 2.3.1 (formal/99-10-07)
• IDL/Java Language Mapping as defined in ptc/00-01-08

The Holder for LongLongSeq. For more information on Holder files see "Generated Files: Holder Files".

org/omg/CORBA/LongLongSeqHolder.java Generated by the IDL-to-Java compiler (portable) version "3.0" from streams.idl 13 May 1999 22:41:36 o'clock GMT+00:00

The Helper for LongSeqHelper. For more information on Helper files see "Generated Files: Helper Files".

org/omg/CORBA/LongSeqHelper.java Generated by the IDL-to-Java compiler (portable) version "3.0" from streams.idl 13 May 1999 22:41:36 o'clock GMT+00:00 The class definition has been modified to conform to the following OMG specifications :

• ORB core as defined by CORBA 2.3.1 (formal/99-10-07)
• IDL/Java Language Mapping as defined in ptc/00-01-08

The Holder for LongSeq. For more information on Holder files see "Generated Files: Holder Files".

org/omg/CORBA/LongSeqHolder.java Generated by the IDL-to-Java compiler (portable) version "3.0" from streams.idl 13 May 1999 22:41:36 o'clock GMT+00:00

The CORBAA request MARSHALor exceptionreply whichfrom the network is thrownstructurally invalid. This error typically indicates whena bug in either the ORBclient-side or server-side run time. For hasexample if a problemreply from the server indicates that the message contains 1000 bytes but the actual message is shorter or longer than 1000 bytes the ORB raises this exception. MARSHAL can also be caused by using the marshallingDII or unmarshallingDSI incorrectly for example if the type of the actual parameters sent does not agree with IDL signature of an operation.

It contains a minor code which gives more detailed information about what caused the exception and a completion status. It may also contain a string describing the exception.

See the section Minor Code Meanings to see the minor codes for this exception. @version 1.18 09/09/97 @since JDK1.2

TheThis CORBAexception indicates that even though the operation that was invoked exists (it has an IDL definition) no implementation for that operation exists. NO_IMPLEMENT exception which is thrown when the implementation can for example be raised by an forORB if a methodclient asks for an object's type definition from the interface repository but no interface repository is notprovided by availablethe ORB.

It contains a minor code which gives more detailed information about what caused the exception and a completion status. It may also contain a string describing the exception.

See the section Minor Code Meanings to see the minor codes for this exception. @version 1.17 09/09/97 @since JDK1.2

Constructs a NO_IMPLEMENT exception with the specified description message minor code and completion status. @param s the String containing a description message @param minor an int specifying the minor code @param completed a CompletionStatus instance indicating the completion status

Constructs a NO_IMPLEMENT exception with the specified minor code and completion status. @param minor an int specifying the minor code @param completed a CompletionStatus instance indicating the completion status

TheException CORBA NO_MEMORY exception which may be thrown by either the client or the server when there is not enough memory for a dynamicthe ORB run time has run out of memory allocation.

It contains a minor code which gives more detailed information about what caused the exception and a completion status. It may also contain a string describing the exception. @see documentation on Java IDL exceptions @version 1.18 09/09/97 @since JDK1.2

TheException CORBA NO_PERMISSION exception which is thrown if thewhen client does not have permission to perform the requestan invocation failed because the caller has insufficient privileges.

It contains a minor code which gives more detailed information about what caused the exception and a completion status. It may also contain a string describing the exception. @see documentation on Java IDL exceptions @version 1.17 09/09/97 @since JDK1.2

The CORBAException thrown NO_RESOURCESwhen exception which is thrown when either thethe ORB has encountered some general resource clientlimitation. For orexample the serverrun does nottime may have sufficientreached the resources to performmaximum permissible number theof open requestconnections.

It contains a minor code which gives more detailed information about what caused the exception and a completion status. It may also contain a string describing the exception. @see documentation on Java IDL exceptions @version 1.17 09/09/97 @since JDK1.2

The CORBAThis exception NO_RESPONSEis exception whichraised if isa client attempts to thrownretrieve whenthe result of a deferred synchronous call but the response tofor the request is not yet available.

It contains a minor code which gives more detailed information about what caused the exception and a completion status. It may also contain a string describing the exception. @see documentation on Java IDL exceptions @version 1.17 09/09/97 @since JDK1.2

Creates a new NamedValue object initialized with the given name value and flag and adds it to the end of this NVList object. The flag can be any one of the argument passing modes: ARG_IN.value ARG_OUT.value or ARG_INOUT.value. @param item_name the name for the new NamedValue object @param valueval an Any object containing the value for the new NamedValue object @param flags one of the following argument modepassing flagsmodes: ARG_IN.value ARG_OUT.value or ARG_INOUT.value @return the newly- created NamedValue object

TheAssociates NameValuePair interface associates a name with a value that is an attribute of an IDL struct. This interfaceand is used in the DynStruct APIs.

The Helper for NameValuePair. For more information on Helper files see "Generated Files: Helper Files".

org/omg/CORBA/NameValuePairHelper.java Generated by the IDL-to-Java compiler (portable) version "3.0" 03 June 1999 11:52:03 o'clock GMT+00:00

The CORBAException raised OBJECT_NOT_EXISTwhenever exceptionan whichinvocation on a deleted object was performed. It is usually thrownan authoritative from"hard" thefault report. Anyone receiving it serveris allowed (even expected) to indicate that the targetdelete all copies of this object doesreference and to perform other appropriate "final recovery" style procedures. Bridges notforward existthis exception to clients also destroying any records they may hold (for example proxy objects used in reference translation). The clients could in turn purge any of their own data structures.

It contains a minor code which gives more detailed information about what caused the exception and a completion status. It may also contain a string describing the exception.

See the section Minor Code Meanings to see the minor codes for this exception. @see documentation on Java IDL exceptions @version 1.13 09/09/97 @since JDK1.2

The CORBAThis exception OBJ_ADAPTERtypically exception which is thrown by the object adapter on theindicates an administrative mismatch for example a server may have servermade an attempt to indicateregister itself with an implementation repository someunder errora name that is already in use or is unknown to the repository.

It contains a minor code which gives more detailed information about what caused the exception and a completion status. It may also contain a string describing the exception.

See the section Minor Code Meanings to see the minor codes for this exception. @see documentation on Java IDL exceptions @version 1.17 09/09/97 @since JDK1.2

A class providing APIs for the CORBA Object Request Broker features. The ORB class also provides "pluggable ORB implementation" APIs that allow another vendor's ORB implementation to be used.

An ORB makes it possible for CORBA objects to communicate with each other by connecting objects making requests (clients) with objects servicing requests (servers).

The ORB class which encapsulates generic CORBA functionality does the following: (Note that items 5 and 6 which include most of the methods in the class ORB are typically used with the Dynamic Invocation Interface (DII) and the Dynamic Skeleton Interface (DSI). These interfaces may be used by a developer directly but most commonly they are used by the ORB internally and are not seen by the general programmer.)

1. initializes the ORB implementation by supplying values for predefined properties and environmental parameters
2. obtains initial object references to services such as the NameService using the method resolve_initial_references
3. converts object references to strings and back
4. connects the ORB to a servant (an instance of a CORBA object implementation) and disconnects the ORB from a servant
5. creates objects such as
   • TypeCode
   • Any
   • NamedValue
   • Context
   • Environment
   • lists (such as NVList) containing these objects
6. sends multiple messages in the DII

The ORB class can be used to obtain references to objects implemented anywhere on the network.

An application or applet gains access to the CORBA environment by initializing itself into an ORB using one of three init methods. Two of the three methods use the properties (associations of a name with a value) shown in the table below.

Standard Java CORBA Properties:

Property Name	Property Value
org.omg.CORBA.ORBClass	class name of an ORB implementation
org.omg.CORBA.ORBSingletonClass	class name of the ORB returned by init()

These properties allow a different vendor's ORB implementation to be "plugged in."

When an ORB instance is being created the class name of the ORB implementation is located using the following standard search order:

1. check in Applet parameter or application string array if any
2. check in properties parameter if any
3. check in the System properties
4. check in the orb.properties file located in the user.home directory (if any)
5. check in the orb.properties file located in the java.home/lib directory (if any)
6. fall back on a hardcoded default behavior (use the Java IDL implementation)

Note that Java IDL provides a default implementation for the fully-functional ORB and for the Singleton ORB. When the method init is given no parameters the default Singleton ORB is returned. When the method init is given parameters but no ORB class is specified the Java IDL ORB implementation is returned.

The following code fragment creates an ORB object initialized with the default ORB Singleton. This ORB has a restricted implementation to prevent malicious applets from doing anything beyond creating typecodes. It is called a singleton because there is only one instance for an entire virtual machine.

 ORB orb = ORB.init(); 

The following code fragment creates an ORB object for an application. The parameter args represents the arguments supplied to the application's main method. Since the property specifies the ORB class to be "SomeORBImplementation" the new ORB will be initialized with that ORB implementation. If p had been null and the arguments had not specified an ORB class the new ORB would have been initialized with the default Java IDL implementation.

 Properties p = new Properties(); p.put("org.omg.CORBA.ORBClass" "SomeORBImplementation"); ORB orb = ORB.init(args p); 

The following code fragment creates an ORB object for the applet supplied as the first parameter. If the given applet does not specify an ORB class the new ORB will be initialized with the default Java IDL implementation.

 ORB orb = ORB.init(myApplet null); 

An application or applet can be initialized in one or more ORBs. ORB initialization is a bootstrap call into the CORBA world. @version 1.70 09/09/97 @since JDK1.2

Connects the given servant object (a Java object that is an instance of the server implementation class) to the ORB. The servant class must extend the ImplBase class corresponding to the interface that is supported by the server. The servant must thus be a CORBA object reference and inherit from org.omg.CORBA.Object. Servants created by the user can start receiving remote invocations after the method connect has been called. A servant may also be automatically and implicitly connected to the ORB if it is passed as an IDL parameter in an IDL method invocation on a non-local object that is if the servant object has to be marshalled and sent outside of the process address space.

Calling the method connect has no effect when the servant object is already connected to the ORB.

Deprecated by the OMG in favor of the Portable Object Adapter APIs. @param obj theThe servant object reference @see CORBA package comments for unimplemented features

Create a TypeCode object for an IDL abstract interface. @param id the logical id for the abstract interface type. @param name the name of the abstract interface type. @return the requested TypeCode. @see CORBA package comments for unimplemented features

See package commentsCreates a basic regardingDynAny unimplementedobject featuresfrom the given TypeCode object.

@param type the TypeCode object from which to create a new DynAny object @return the new DynAny object created from the given TypeCode object @throws org.omg.CORBA.ORBPackage.InconsistentTypeCode if the given TypeCode object is not consistent with the operation. @see CORBA package comments for unimplemented features @see DynamicAny package replaces these API

See packageCreates a commentsnew DynAny regarding unimplementedobject from featuresthe given Any object.

@param value the Any object from which to create a new DynAny object @return the new DynAny object created from the given Any object @see CORBA package comments for unimplemented features @see DynamicAny package replaces these API

See package commentsCreates a new regardingDynArray unimplementedobject featuresfrom the given TypeCode object.

@param type the TypeCode object from which to create a new DynArray object @return the new DynArray object created from the given TypeCode object @throws org.omg.CORBA.ORBPackage.InconsistentTypeCode if the given TypeCode object is not consistent with the operation. @see CORBA package comments for unimplemented features @see DynamicAny package replaces these API

See package commentsCreates a new regardingDynEnum unimplementedobject featuresfrom the given TypeCode object.

@param type the TypeCode object from which to create a new DynEnum object @return the new DynEnum object created from the given TypeCode object @throws org.omg.CORBA.ORBPackage.InconsistentTypeCode if the given TypeCode object is not consistent with the operation. @see CORBA package comments for unimplemented features @see DynamicAny package replaces these API

See package commentsCreates a new regardingDynSequence unimplementedobject featuresfrom the given TypeCode object.

@param type the TypeCode object from which to create a new DynSequence object @return the new DynSequence object created from the given TypeCode object @throws org.omg.CORBA.ORBPackage.InconsistentTypeCode if the given TypeCode object is not consistent with the operation. @see CORBA package comments for unimplemented features @see DynamicAny package replaces these API

See package commentsCreates a new regardingDynStruct unimplementedobject featuresfrom the given TypeCode object.

@param type the TypeCode object from which to create a new DynStruct object @return the new DynStruct object created from the given TypeCode object @throws org.omg.CORBA.ORBPackage.InconsistentTypeCode if the given TypeCode object is not consistent with the operation. @see CORBA package comments for unimplemented features @see DynamicAny package replaces these API

See package commentsCreates a new regardingDynUnion unimplementedobject featuresfrom the given TypeCode object.

@param type the TypeCode object from which to create a new DynUnion object @return the new DynUnion object created from the given TypeCode object @throws org.omg.CORBA.ORBPackage.InconsistentTypeCode if the given TypeCode object is not consistent with the operation. @see CORBA package comments for unimplemented features @see DynamicAny package replaces these API

Create a TypeCode object for an IDL fixed type. @param digits specifies the total number of decimal digits in the number and must be from 1 to 31 inclusive. @param scale specifies the position of the decimal point. @return the requested TypeCode. @see CORBA package comments for unimplemented features

Create a TypeCode object for an IDL native type. @param id the logical id for the native type. @param name the name of the native type. @return the requested TypeCode. @see CORBA package comments for unimplemented features

See package comments regarding unimplementedCan be invoked to create featuresnew instances of policy objects of a specific type with specified initial state. If create_policy fails to instantiate a new Policy object due to its inability to interpret the requested type and content of the policy it raises the PolicyError exception with the appropriate reason. @seeparam type the PolicyType of the policy object to be created @param val the value that will be used to set the initial state of the Policy object that is created @return Reference to a newly created Policy object of type specified by the type parameter and initialized to a state specified by the val parameter @throws org.omg.CORBA.PolicyError when the requested policy is not supported package commentsor a requested initial state for unimplementedthe policy featuresis not supported.

Creates a TypeCode object representing a a recursive IDL sequence.

For the IDL struct FooNode in following code fragment the offset parameter for creating its sequence would be 1:

 Struct FooNode { long value; Sequence <FooNode> Chainsubnodes; }; 

@param bound the bound for the sequence 0 if unbounded @param offset the index to the enclosing TypeCode object that describes the elements of this sequence @return a newly-created TypeCode object describing a recursive sequence @deprecated Use a combination of create_recursive_tc and create_sequence_tc instead @see #create_recursive_tc(String) create_recursive_tc @see #create_sequence_tc(int TypeCode) create_sequence_tc

Create a recursive TypeCode object which serves as a placeholder for a concrete TypeCode during the process of creating TypeCodes which contain recursion. The id parameter specifies the repository id of the type for which the recursive TypeCode is serving as a placeholder. Once the recursive TypeCode has been properly embedded in the enclosing TypeCode which corresponds to the specified repository id it will function as a normal TypeCode. Invoking operations on the recursive TypeCode before it has been embedded in the enclosing TypeCode will result in undefineda BAD_TYPECODE behaviorexception.

For example the following IDL type declarationsdeclaration containcontains recursion:

 Struct FooNode { long value; Sequence <FooNode> Chain; }; Struct Bar { public Bar membersubnodes; }; 

To create a TypeCode for struct BarNode you would invoke the TypeCode creation operations as shown below:

 String barIDnodeID = "IDL:BarNode:1.0"; TypeCode recursiveTCrecursiveSeqTC = orb.create_sequence_tc(0 orb.create_recursive_tc(barIDnodeID)); StructMember[] members = { new StructMember("membersubnodes" recursiveTCrecursiveSeqTC null) }; TypeCode structBarTCstructNodeTC = orb.create_struct_tc(barIDnodeID "BarNode" members); 

Also note that the following is an illegal IDL type declaration:

 Struct Node { Node next; }; 

Recursive types can only appear within sequences which can be empty. That way marshaling problems when transmitting the struct in an Any are avoided.

@param id the logical id of the referenced type @return the requested TypeCode @see CORBA package comments for unimplemented features

Creates a TypeCode object representing an IDL sequence. The TypeCode object is initialized with the given bound and element type. @param bound the bound for the sequence 0 if unbounded @param element_type the TypeCode object describing the elements contained in the sequence @return a newly-created TypeCode object describing an IDL sequence

Creates a TypeCode object for an IDL value box. @param id the logical id for the value type @param name the name of the value type @param boxed_type the TypeCode for the type @return the requested TypeCode @see CORBA package comments for unimplemented features

Create a TypeCode object for an IDL value type. The concrete_base parameter is the TypeCode for the immediate concrete valuetype base of the valuetype for which the TypeCode is being created. It may be null if the valuetype does not have a concrete base. @param id the logical id for the value type. @param name the name of the value type. @param type_modifier one of the value type modifier constants: VM_NONE VM_CUSTOM VM_ABSTRACT or VM_TRUNCATABLE @param concrete_base a TypeCode object describing the concrete valuetype base @param members an array containing the members of the value type @return the requested TypeCode @see CORBA package comments for unimplemented features

Destroys the ORB instance and freesso that its allresources can be reclaimed. Any operation invoked on a destroyed ORB reference will throw the resourcesOBJECT_NOT_EXIST exception. underOnce an ORB instancehas been destroyed another call to init with the same ORBid will return a reference to a newly constructed ORB.

TheIf methoddestroy is called on an ORB that has not implementedbeen shut down it will start the shut down process and block until the ORB has shut down before it destroys the ORB.
If an application calls destroy The APIin a thread that is providedcurrently toservicing an invocation the BAD_INV_ORDER system conformexception will be thrown with the OMG specminor code 3 since blocking would result in a deadlock.

For maximum portability and to avoid resource leaks an application should always call shutdown and destroy on all ORB instances before exiting. @throws org.omg.CORBA.BAD_INV_ORDER if the current thread is servicing an invocation

Disconnects the given servant object from the ORB. After this method returns the ORB will reject incoming remote requests for the disconnected servant and will send the exception org.omg.CORBA.OBJECT_NOT_EXIST back to the remote client. Thus the object appears to be destroyed from the point of view of remote clients. Note however that local requests issued using the servant directly do not pass through the ORB; hence they will continue to be processed by the servant.

Calling the method disconnect has no effect if the servant is not connected to the ORB.

Deprecated by the OMG in favor of the Portable Object Adapter APIs. @param obj The servant object to be disconnected from the ORB @see CORBA package comments for unimplemented features

Retrieves a Current object. The Current interface is used to manage thread-specific information for use by services such as transactions and security. @see CORBA package comments for unimplemented features @return a newly-created Current object @deprecated use resolve_initial_references. @see CORBA package comments for unimplemented features.

See package comments regarding unimplementedUsed to obtain information about featuresCORBA facilities and services that are supported by this ORB. The service type for which information is being requested is passed in as the in parameter service_type the values defined by constants in the CORBA module. If service information is available for that type that is returned in the out parameter service_info and the operation returns the value true. If no information for the requested services type is available the operation returns false (i.e. the service is not supported by this ORB).

@param service_type a short indicating the service type for which information is being requested @param service_info a ServiceInformationHolder object that will hold the ServiceInformation object produced by this method @return true if service information is available for the service_type; false if no information for the requested services type is available @see CORBA package comments for unimplemented features

Performs an implementation-dependent unit of work if called by the main thread. Otherwise it does nothing. The methods work_pending and perform_work can be used in conjunction to implement a simple polling loop that multiplexes the main thread among the ORB and other activities. @see CORBA package comments for unimplemented features

This operation returnsblocks when the ORB has shutdown. Ifcurrent called bythread until the main threadORB it enableshas completed the ORBshutdown to perform work using the mainprocess initiated when some thread calls threadshutdown. Otherwise it simply waits until the ORB hasIt may be used by multiple threads which shutdown.get @seeall CORBAnotified package comments for unimplementedwhen the ORB shuts featuresdown.

Instructs the ORB to shut down which causes all object adapters to shut down in preparation for destruction.
If the wait_for_completion parameter is true this operation blocks until all ORB processing (including processing of currently executing requests object deactivation and other object adapter operations) has completed. If an application does this in a thread that is currently servicing an invocation the BAD_INV_ORDER system exception will be thrown with the OMG minor code 3 since blocking would result in a deadlock.
If the wait_for_completion parameter is FALSE then shutdown may not have completed upon return.

While the ORB is in the process of shutting down the ORB operates as normal servicing incoming and outgoing requests until all requests have been completed. Once an ORB has shutdown only object reference management operations may be invoked on the ORB or any object reference obtained from it. An application may also invoke the destroy operation on the ORB itself. Invoking any other operation will throw the BAD_INV_ORDER system exception with the OMG minor code 4.

The ORB.run method will return after shutdown has been called. @param wait_for_completion true to indicateif that the ORBcall should completeblock processinguntil the before shutting downshutdown is complete; false to indicateif that the ORBit should shut downreturn immediately @seethrows org.omg.CORBA.BAD_INV_ORDER if package commentsthe current forthread is servicing unimplementedan featuresinvocation

Returns true if the ORB needs the main thread to perform some work and false if the ORB does not need the main thread. @return true if there is work pending meaning that the ORB needs the main thread to perform some work; false if there is no work pending and thus the ORB does not need the main thread @see CORBA package comments for unimplemented features

The Holder for Object. For more information on Holder files see "Generated Files: Holder Files".

A Holder class for a CORBA object reference (a value of type org.omg.CORBA.Object). It is usually used to store "out" and "inout" parameters in IDL methods. If an IDL method signature has a CORBA Object reference as an "out" or "inout" parameter the programmer must pass an instance of ObjectHolder as the corresponding parameter in the method invocation; for "inout" parameters the programmer must also fill the "in" value to be sent to the server. Before the method invocation returns the ORB will fill in the value corresponding to the "out" value returned from the server.

If myObjectHolder is an instance of ObjectHolder the value stored in its value field can be accessed with myObjectHolder.value. @version 1.14 09/09/97 @since JDK1.2

The Helper for OctetSeq. For more information on Helper files see "Generated Files: Helper Files".

org/omg/CORBA/OctetSeqHelper.java Generated by the IDL-to-Java compiler (portable) version "3.0" from streams.idl 13 May 1999 22:41:36 o'clock GMT+00:00 The class definition has been modified to conform to the following OMG specifications :

• ORB core as defined by CORBA 2.3.1 (formal/99-10-07)
• IDL/Java Language Mapping as defined in ptc/00-01-08

The Holder for OctetSeq. For more information on Holder files see "Generated Files: Holder Files".

org/omg/CORBA/OctetSeqHolder.java Generated by the IDL-to-Java compiler (portable) version "3.0" from streams.idl 13 May 1999 22:41:36 o'clock GMT+00:00

The CORBAThis exception PERSIST_STOREindicates exceptiona