All Packages from org.omg.IOP.CodecFactoryPackage.* to org.omg.IOP.CodecPackage.*

Home >> All >> org >> omg >> [ IOP Javadoc ]

•

• org.omg.IOP: Javadoc index of package org.omg.IOP.

Package Samples:

• org.omg.IOP.CodecPackage
• org.omg.IOP.CodecFactoryPackage

Classes:

• TaggedProfile: The TaggedProfile if part of the IOR , defining a single specific aspect of the object related information. The content of profile depends on this information. It is represented here just as an array of bytes. The OMG currently defines three types of the tagged profile: The Internet profile, identified by TAG_INTERNET_IOP , supports the Internet Inter-ORB Protocol. The Multiple Components profile, identified by TAG_MULTIPLE_COMPONENTS , may be used to carry various IOR tagged components. The SCCP IOP profile (described in OMG CORBA/IN Interworking specification). The tagged profile may have its ...
• IOR: The object IOR contains sufficient information for finding local or remote CORBA object. It also contains additional data like the object native and supported char sets, URLs to download the required additional java classes and so on. IOR can define multiple alternative addresses for the same object or indicate that the object is equal to null. The IOR is a standard structure, transferred when sending an object with OutputStream.write_Object(org.omg.CORBA.Object) > OutputStream.write_Object(org.omg.CORBA.Object) 55 and receiving with InputStream.read_Object() > InputStream.read_Object() 55 . The ...
• Codec: Codec provides means to encode IDL data types into the byte arrays. Some parts of the CORBA message may contain such abstracted (encapsulated) byte arrays, holding arbitrary information. The encoding and decoding operations are defined separately in CodecOperations . The Codec for ENCODING_CDR_ENCAPS v 1.0 - 1.2 is required by OMG. Vendors can implement additional Codec's, driven by alternative algorithms. The ENCODING_CDR_ENCAPS Codec, returned by the CodecFactory , is a local object. It is not possible to get its stringified reference, to send it over CDR streams or invoke the methods remotely. ...
• TaggedComponent: The tagged component in a part of the TaggedProfile . The examples of the possible components inside the tag are TAG_CODE_SETS , TAG_ALTERNATE_IIOP_ADDRESS , TAG_JAVA_CODEBASE , TAG_ORB_TYPE and TAG_POLICIES . The complete list (over 20 possible components) can be found in OMG specification. Some of these components occur only once (in the same TaggedProfile), others can be repeated.
• TAG_CODE_SETS: Holds the integer identifier of the code sets profile. The code sets profile provides information about the native and supported encodings for the "narrow" (usually 8 bit) and "wide" (usually 16 bit) characters. In Gnu Classpath implementation the class, responsible for providing this information is gnu.CORBA.CharSets_OSF . If this profile is missing, it is assumed, that the "narrow" characters are encoded in ISO 8859-1. However there is no default encoding for the "wide" characters, and, if this profile is missing, the INV_OBJREF minor code 1 is thrown. The "narrow" characters are used in char ...
• TAG_ORB_TYPE: Holds an integer constant of the TAG_ORB_TYPE Component that defines the kind or CORBA implementation of ORB the reference is comming from. This information may be useful to work around problems with that particular ORB, or exploit shared efficiencies. This tag contains a single unsigned long value; these values are managed by OMG group. Anyone may register any ORB types by submitting a one-paragraph description of the ORB type to the OMG, and will receive a new ORB type ID in return. A list of all ORB type descriptions should be available on the OMG web server. TODO Register the GNU Classpath ...
• ExceptionDetailMessage: Defines the ExceptionDetailMessage (= 14) service context. This context may be included into reply message, having the SYSTEM_EXCEPTION or USER_EXCEPTION reply status, as the alternative to the stack trace that might contain sensitive or unwanted information. The service context contains the CDR-encapsulated wide string, usually returned by Throwable.getMessage() > Throwable.getMessage() 55 . The applications may also send the more comprehensive UnknownExceptionInfo ( = 9 ) service context that contains the thrown exception, written as the Value type.
• CodeSets: Holds the integer identifier of the CodeSets context. This context consist of this identifier, followed by two standard codes, first for narrow and second for wide character sets. The charset codes are integer (CORBA long) constants. Usually "narrow" means 8 bit and "wide" means 16 bit, but under specific circumstances these two charsets may be identical. The context is optional for "narrow" characters (assuming the charset code 0x00010001 = ISO 8859-1). It is required if the "wide" characters are transferred. They standard charset values are managed in gnu.CORBA.GIOP.CharSets_OSF .
• CodecFactory: The CodecFactory is used to obtaind Codec for the given encoding. The obtaining operations are defined separately in CodecFactoryOperations . The CodecFactory is a local object. It is not possible to get its stringified reference, to send it over CDR streams or invoke the methods remotely. CodecFactory is returned by ORB.resolve_initial_references("CodecFactory") .
• InvalidTypeForEncoding: This exception is raised by CodecOperations.encode(org.omg.CORBA.Any) > CodecOperations.encode(org.omg.CORBA.Any) 55 or CodecOperations.encode_value(org.omg.CORBA.Any) > CodecOperations.encode_value(org.omg.CORBA.Any) 55 when the type is not valid for the encoding. For instance, the "wide" character string is not a valid type for GIOP version 1.0.
• FormatMismatch: This exception is raised by CodecOperations.decode(byte[]) > CodecOperations.decode(byte[]) 55 or CodecOperations.decode_value(byte[], org.omg.CORBA.TypeCode) > CodecOperations.decode_value(byte[], org.omg.CORBA.TypeCode) 55 when the data in the octet sequence cannot be decoded into org.omg.CORBA.Any .
• TAG_RMI_CUSTOM_MAX_STREAM_FORMAT: A single constant interface, defining the TAG_RMI_CUSTOM_MAX_STREAM_FORMAT (= 38) tagged component. This component defines the format that has been used to write the RMI-IIOP value type objects in the message. It consists of the single byte, having the value of the used version. If this component is missing, the default value is assumed to be 1 for GIOP 1.2 and 2 for GIOP 1.3. The component can occur only once in the same IOR profile.
• RMICustomMaxStreamFormat: A single constant interface, defining the RMICustomMaxStreamFormat (= 17) service context. This constant is used in the service contexts inside the message when the TAG_RMI_CUSTOM_MAX_STREAM_FORMAT are used in IOR references. Please note that these two constants have different values.
• TAG_JAVA_CODEBASE: Holds an integer identifier of the TAG_JAVA_CODEBASE profile. This profile provides a space separated list of URLs, from where the required stubs and ties can be downloaded. The this IOR profile component is used to provide the code source for stubs and ties. The code source for values and value helpers is transmitted when transferring the value itself.
• ServiceContext: The ServiceContext structure contains the service data, being passed in the CORBA message. For instance, then passing the wide characters, it is mandatory to include the service context, defining the used encoding. The contexts are recognised by they integer indentifier. In this class, the content of the context is represented as an abstract array of bytes.
• UnknownEncoding: The CodecFactoryOperations.create_codec(org.omg.IOP.Encoding) > CodecFactoryOperations.create_codec(org.omg.IOP.Encoding) 55 raises UnknownEncoding if that factory cannot create a org.omg.IOP.Codec of the given encoding.
• TAG_ALTERNATE_IIOP_ADDRESS: Holds an integer constant of the TAG_ALTERNATE_IIOP_ADDRESS Component that may occur zero or more times in the Internet of Multiple components profile. The tag contains the possible alternative address (host and port) of the object being defined by IOR profile. This tag is supported since GIOP 1.2.
• Encoding: Defines the encoding format of the Codec , including the major and minor version numbers. The only currently supported encodings are ENCODING_CDR_ENCAPS versions 1.1 - 1.2. Vendors can implement additional encodings.
• MultipleComponentProfileHolder: A holder for the sequence of TaggedComponent ( MultipleComponentProfileHelper ).
• ENCODING_CDR_ENCAPS: Holds an integer identifier of the ENCODING_CDR_ENCAPS encoding. This is the only encoding, required by OMG specification. Apart the encoding format integer identifier, the encoding record contains the GIOP version number.
• TAG_INTERNET_IOP: Holds the integer identifier of the internet profile. The internet profile contains (in the given order) a supported GIOP version, an address of the remote host, a port of the remote host and an object key as the byte array.
• TransactionService: Holds the integer identifier of the TransactionService context. The content of that data structure is defined by OMG as CosTransactions::PropogationContext in the Object Transaction Service specification (formal/00-06-28).
• TypeMismatch: The TypeMismatch may be thrown by various methods in org.omg.DynamicAny package when the operation is not applicable due unexpected org.omg.CORBA.TypeCode .
• TAG_POLICIES: An integer identifier for the TAG_POLICIES component. This component contains the sequence of QoS (Quality of Service) policies exported with the object reference by an object adapter.
• UnknownEncodingHelper: The helper operations for the exception UnknownEncoding .

Home | Contact Us | Privacy Policy | Terms of Service