| Home >> All >> org >> omg |
Page 1 2 3 4 5
| • | org.omg.CORBA.* (219) | • | org.omg.CORBA_2_3.* (5) | • | org.omg.CSI.* (62) |
| • | org.omg.CosEventChannelAdmin.* (62) | • | org.omg.CosEventComm.* (35) | • | org.omg.CosNaming.* (62) |
| • | org.omg.CosNotification.* (99) | • | org.omg.CosNotifyChannelAdmin.* (171) | • | org.omg.CosNotifyComm.* (115) |
| • | org.omg.CosNotifyFilter.* (81) |
Package Samples:
• org.omg.CORBA.DynAnyPackage: This package provides the support of OMG CORBA ; see overview of the implemented functionality.
• org.omg.CORBA.portable: This package provides the support of OMG CORBA ; see overview of the implemented functionality.
• org.omg.CORBA.TypeCodePackage: This package provides the support of OMG CORBA ; see overview of the implemented functionality.
• org.omg.CORBA_2_3.portable: This package supports the ORB extendsions that appeared since CORBA 2_3.
• org.omg.CosNaming.NamingContextPackage: The CosNaming package generated from the IDL.
• org.omg.CSI
• org.omg.CosEventChannelAdmin
• org.omg.CosEventComm
• org.omg.CosNaming
• org.omg.CosNotification
• org.omg.CosNotifyChannelAdmin
• org.omg.CosNotifyComm
• org.omg.CosNotifyFilter
• org.omg.CORBA.ORBPackage
• org.omg.CORBA_2_3
• org.omg.CosNaming.NamingContextExtPackage
Classes:
• ServerRequestInfoOperations: Provides request information, accessible for the ClientRequestInterceptor . Some methods of this interface are not valid at all interception points. The following table shows the validity of each method. If it is not valid, BAD_INV_ORDER minor 14 will be thrown. receive_request_ service_contexts 55 receive_request 55 send_reply 55 send_exception 55 send_other 55 Inherited from RequestInfoOperations : arguments 55 no yes 1 yes no 2 no 2 exceptions 55 no yes contexts 55 no yes operation_context 55 no yes yes no no result 55 no no yes no no reply_status 55 no no yes * forward_reference 55 no yes 2 ...
• ClientRequestInfoOperations: Provides request information, accessible for the ClientRequestInterceptor . Some methods of this interface are not valid at all interception points. The following table shows the validity of each method. If it is not valid, BAD_INV_ORDER minor 14 will be thrown. send_request 55 send_poll 55 receive_reply 55 receive_exception 55 receive_other 55 Inherited from RequestInfoOperations : arguments 55 yes 1 no yes no no exceptions 55 yes no yes contexts 55 yes no yes operation_context 55 yes no yes result 55 no no yes no no sync_scope 55 yes no yes reply_status 55 no no yes forward_reference 55 no no ...
• MARSHAL: Means that some request or reply from the network has a wrong size or is structurally invalid. In GNU Classpath, this exception may have the following minor codes (the high 20 bits being Classpath VMCID): Hex Dec Minor Name Case 47430001 1195573249 1 Giop The message being received is not a GIOP message. It does not start from the expected magic sequence byte[] { 'G', 'I', 'O', 'P' }. 47430002 1195573250 2 Header The unexpected IOException while reading or writing the GIOP message header or the subsequent request or response header 47430003 1195573251 3 EOF The data stream ended before reading ...
• ORB: A central class in CORBA implementation, responsible for sending and handling remote invocations. ORB also works as a factory for creating instances of certain CORBA classes. Despite the core library contains the fully working CORBA implementation, it also provides a simple way to plug-in the alternative CORBA support. This is done by replacing the ORB. The alternative ORB can be specified via properties, passed to ORB.Init(...). When creating an ORB instance, the class name is searched in the following locations: 1. Applet parameter or application string array, if any. 2. The properties parameter, ...
• ORBInitializer: Registers the interceptor. Direct interceptor registration would open a security hole. Hence instead the interceptors from the ORB.init(..) method, passing the names of the needed initialized classes via properties. These property names are of the form org.omg.PortableInterceptor.ORBInitializerClass.<Service> where <Service> is the string name of a class, which implements ORBInitializer . During ORB.init(..) , the properties begining with org.omg.PortableInterceptor.ORBInitializerClass are collected, the <Service> portion of each property is extracted, the initialiser is instantiated ...
• Current: The portable interceptor Current (PICurrent) contains multiple slots where an interceptor can rememeber the request - specific values between subsequent calls of the interceptor methods. In multithreaded environment, it is not possible just to store such data in the interceptor object fields. On the client side, it is possible to set the initial slot values by modifying slots on the Current, returend by ORB.resolve_initial_references ("PICurrent"). The returned value is narrowed with the CurrentHelper.narrow(org.omg.CORBA.Object) 55 . On the subsequent invocation, made from the same thread, the ...
• Servant: The servant is responsible for handling the method invocation on the target object. It can be one servant per object, or the same servant can support several (possibly all) objects, associated with the given POA. Till JDK 1.3 inclusive, a typical IDL to java compiler generates an implementation base (name pattern _*ImplBase.java) that is derived from the org.omg.CORBA.portable.ObjectImpl . Since JDK 1.4 the implementation base is derived from the Servant, also having a different name pattern (*POA.java). This suffix may be confusing, as the servant itself is not POA nor it is derived from it. In ...
• BAD_OPERATION: Means that the object exists but does not support the operation that was invoked on it. In GNU Classpath, this exception may have the following Minor codes: Hex Dec Minor Name Case 47430000 1195573248 0 Method The remote side requested to invoke the method that is not available on that target (client and server probably disagree in the object definition). This code is set when the problem arises in the Classpath core; the idlj and rmic may generate the user code that sets 0x0 or other value. 47430009 1195573257 9 Any Attempt to extract from the Any value of the different type that was stored into ...
• 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. ...
• RequestProcessingPolicyValue: Specifies the behaviour in the case when the requested object is not found in the Active Object Map or that map is not in use. The map is not in use when the ServantRetentionPolicyValue.NON_RETAIN 55 policy is active. USE_ACTIVE_OBJECT_MAP_ONLY Raise an org.omg.CORBA.OBJECT_NOT_EXIST with the minor code 2. ServantRetentionPolicyValue.RETAIN 55 policy is also required. USE_DEFAULT_SERVANT Dispatch request to the default servant. If no such exists, raise org.omg.CORBA.OBJ_ADAPTER with minor code 3. IdUniquenessPolicyValue.MULTIPLE_ID 55 is also required. USE_SERVANT_MANAGER Dispatch request to the ...
• ThreadPolicyValue: Defines the possible values for the POA thread policy. This enumeration can obtain the following values: ORB_CTRL_MODEL Each object in POA has a separate serving thread and a separate server socket, listening on the objects individual port. Additionally, when the request is accepted, it is also served in a separate thread, so several requests to the same object can be processed in parallel. The servant can always get the Id and POA of the object it is currently serving by invoking Servant._object_id() 55 and Servant._poa() 55 . These two methods use thread to data map and must work correctly even ...
• ValueBase: ValueBase is the basic interface for all CORBA value data types. A value type is something between CORBA structure and CORBA object. Like CORBA object, it can have methods, supporting some IDL-defined interface. However, like structures, they are local and passed by value, not by IOR reference. Unlike CORBA objects, values are not connected to any ORB by default; they hanlde the implemented functionality locally. The classes, required to implement that functionality, should either be pre-defined or they can be downloaded from the certain URL, defined as CodeBase. The value types can have both public ...
• Current: Provides the Id of the object currently being served and POA to that this object is connected. Both Id and POA can be simpler obtained from the servant by Servant._object_id() 55 and Servant._poa() 55 that use POA Current indirectly. The operations on Current for obtaining these data are defined in CurrentOperations . As long as the ORB reference is still available, the current information is available via Current that is returned by ORB.resolve_initial_references("POACurrent"). To support this call, the ORB maintains the thread to invocation data map for all calls that are currently being processed ...
• CookieHolder: The CookieHolder is used together with the org.omg.PortableServer.ServantLocator , allowing the ServantLocatorOperations.preinvoke(byte[], org.omg.PortableServer.POA, java.lang.String, org.omg.PortableServer.ServantLocatorPackage.CookieHolder) > ServantLocatorOperations.preinvoke(byte[], org.omg.PortableServer.POA, java.lang.String, org.omg.PortableServer.ServantLocatorPackage.CookieHolder) 55 to return an arbitrary java.lang.Object that will be later passed to ServantLocatorOperations.postinvoke(byte[], org.omg.PortableServer.POA, java.lang.String, java.lang.Object, org.omg.PortableServer.Servant) ...
• ServantActivatorPOA: This ServantActivator stub is an optional base for the servant activators. This stub cannot serve remote invocations, as methods in ServantActivatorOperations take POA as one of parameters. Both JDK 1.5 API and OMG specifies that POA is a local object that must not be transferred to the remote invocation target. You do not need to derive your servant activator from this stub, it is enough to implement the ServantActivator interface. But you may choose to do this if you need the functional _all_interfaces(POA, byte[]) 55 method or want to keep default behavior during the incarnation or etherialization ...
• ServantLocatorPOA: The ServantLocator stub is an optional base for the servant locators. It cannot serve remote invocations, as methods in ServantLocatorOperations take POA as one of parameters. Both JDK 1.5 API and OMG specifies that POA is a local object that must not be transferred to the remote invocation target. You do not need to derive your servant locator from this stub, it is enough to implement the ServantLocator interface. But you may choose to do this if you need its functional gnuServantObject._ids() > gnuServantObject._ids() 55 method or want to keep default behaviour during pre- or post- invokcations ...
• _ServantActivatorStub: This ServantActivator stub is an optional base for the servant activators. This stub cannot accept remote invocations, as methods in ServantActivatorOperations take POA as one of parameters. Both JDK 1.5 API and OMG specifies that POA is a local object that must not be transferred to the remote invocation target. You do not need to derive your servant activator from this stub, it is enough to implement the ServantActivator interface. But you may choose to do this if you need the functional _ids() 55 method or want to keep default behavior during the incarnation or etherialization.
• DynAny: The DynAny interface provides possibility to access the components of the CORBA object, stored inside the org.omg.CORBA.Any . The DynAny and derived classes additionally allows to access the members of the sequence, structure, union and get the data about enumeration, value type and CORBA fixed without knowing the exact type at the run time. The returned members are also wrapped into DynAny objects, allowing them to be the nested structures. The DynAny's are usually produced by DynAnyFactory . This factory is obtained from the ORB: DynAnyFactory f = DynAnyFactoryHelper.narrow (orb.resolve_initial_references("DynAnyFactory")); ...
• 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.
• _ServantLocatorStub: The ServantLocator stub is an optional base for the servant locators. This stub cannot accept remote invocations, as methods in ServantLocatorOperations take POA as one of parameters. Both JDK 1.5 API and OMG specifies that POA is a local object that must not be transferred to the remote invocation target. You do not need to derive your servant locator from this stub, it is enough to implement the ServantLocator interface. But you may choose to do this if you need its functional _ids() 55 method or want to keep default behavior during per- or post- invokcations.
• NO_RESOURCES: Means that the ORB has reached some general resource limitation like maximal number of the opened connections. In GNU Classpath, this exception may have the following minor codes: Hex Dec Minor Name Case 47430014 1195573268 20 Ports No more free ports available for the new objects. The port control, if turned on, prevents malicios client from knocking the server out by suddenly requiring to allocate a very large number of objects. 47430015 1195573269 21 Threads Too many parallel calls (too many parallel threads). The thread control, if turned on, prevents malicios client from knocking the server ...
• NameDynAnyPairSeqHelper: A helper operations for the array of NameDynAnyPair ( NameDynAnyPairSeq ). Following the 1.5 JDK specifications, DynAny (and hence the sequence of structures, containing DynAny) is always a local object. Hence the two methods of this helper ( read(org.omg.CORBA.portable.InputStream) 55 and write(org.omg.CORBA.portable.OutputStream, org.omg.DynamicAny.NameDynAnyPair[]) 55 are not in use, always throwing org.omg.CORBA.MARSHAL .
• OMGVMCID: The higher 20 bits of any CORBA exception hold "Vendor Minor Codeset ID" (VMCID), for instance 0x4F4D0000 (OMG standard), 0x54410000 (TAO), 0x4A430000 (JacORB), 0x49540000 (IONA), 0x53550000 (Sun). GNU Classpath official vendor minor code set id is 0x47430000 ("GC\x00\x00"), and the reserved space spans till 0x47430FFF, allowing to use up to 4096 Classpath specific exceptions. It was assigned 30/09/2005 by OMG Vice President Andrew Watson. The standard minor codes for the standard system exceptions are prefaced by the VMCID assigned to OMG, defined as 0x4F4D0000 (the code of the minor field for ...
| Home | Contact Us | Privacy Policy | Terms of Service |