-
- All Known Subinterfaces:
- ORBInitializer
public interface ORBInitializerOperations
Facilitates interceptor registration and ORB initialization.Interceptors are intended to be a means by which ORB services gain access to ORB processing, effectively becoming part of the ORB. Since Interceptors are part of the ORB, when
ORB.init
returns an ORB, the Interceptors shall have been registered. Interceptors cannot be registered on an ORB after it has been returned by a call toORB.init
.An Interceptor is registered by registering an associated
ORBInitializer
object which implements theORBInitializer
interface. When an ORB is initializing, it shall call each registeredORBInitializer
, passing it anORBInitInfo
object which is used to register its Interceptor.Registering ORB Initializers in Java
ORBInitializers are registered via Java ORB properties.
The property names are of the form:
whereorg.omg.PortableInterceptor.ORBInitializerClass.<Service>
<Service>
is the string name of a class which implements
To avoid name collisions, the reverse DNS name convention should be used. For example, if company X has three initializers, it could define the following properties:org.omg.PortableInterceptor.ORBInitializer
org.omg.PortableInterceptor.ORBInitializerClass.com.x.Init1
org.omg.PortableInterceptor.ORBInitializerClass.com.x.Init2
org.omg.PortableInterceptor.ORBInitializerClass.com.x.Init3
org.omg.PortableInterceptor.ORBInitializerClass
shall be collected, the<Service>
portion of each property shall be extracted, an object shall be instantiated with the<Service>
string as its class name, and thepre_init
andpost_init
methods shall be called on that object. If there are any exceptions, the ORB shall ignore them and proceed.Example
A client-side logging service written by company X, for example, may have the following ORBInitializer implementation:
To run a program calledpackage com.x.logging; import org.omg.PortableInterceptor.Interceptor; import org.omg.PortableInterceptor.ORBInitializer; import org.omg.PortableInterceptor.ORBInitInfo; public class LoggingService implements ORBInitializer { void pre_init( ORBInitInfo info ) { // Instantiate the Logging Service s Interceptor. Interceptor interceptor = new LoggingInterceptor(); // Register the Logging Service s Interceptor. info.add_client_request_interceptor( interceptor ); } void post_init( ORBInitInfo info ) { // This service does not need two init points. } }
MyApp
using this logging service, the user could type:java -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.x.Logging.LoggingService MyApp
Notes about Registering Interceptors
Request Interceptors are registered on a per-ORB basis.
To achieve virtual per-object Interceptors, query the policies on the target from within the interception points to determine whether they should do any work.
To achieve virtual per-POA Interceptors, instantiate each POA with a different ORB. While Interceptors may be ordered administratively, there is no concept of order with respect to the registration of Interceptors. Request Interceptors are concerned with service contexts. Service contexts have no order, so there is no purpose for request Interceptors to have an order. IOR Interceptors are concerned with tagged components. Tagged components also have no order, so there is no purpose for IOR Interceptors to have an order.
Registration code should avoid using the ORB (i.e., calling
ORB.init
with the providedorb_id
). Since registration occurs during ORB initialization, results of invocations on this ORB while it is in this state are undefined.- See Also:
ORBInitInfo
-
-
Method Summary
Methods Modifier and Type Method and Description void
post_init(ORBInitInfo info)
Called during ORB initialization.void
pre_init(ORBInitInfo info)
Called during ORB initialization.
-
-
-
Method Detail
-
pre_init
void pre_init(ORBInitInfo info)
Called during ORB initialization. If it is expected that initial services registered by an interceptor will be used by other interceptors, then those initial services shall be registered at this point via calls toORBInitInfo.register_initial_reference
.- Parameters:
info
- provides initialization attributes and operations by which Interceptors can be registered.
-
post_init
void post_init(ORBInitInfo info)
Called during ORB initialization. If a service must resolve initial references as part of its initialization, it can assume that all initial references will be available at this point.Calling the
post_init
operations is not the final task of ORB initialization. The final task, following thepost_init
calls, is attaching the lists of registered interceptors to the ORB. Therefore, the ORB does not contain the interceptors during calls topost_init
. If an ORB-mediated call is made from withinpost_init
, no request interceptors will be invoked on that call. Likewise, if an operation is performed which causes an IOR to be created, no IOR interceptors will be invoked.- Parameters:
info
- provides initialization attributes and operations by which Interceptors can be registered.
-
-
Deutsche Übersetzung
Sie haben gebeten, diese Seite auf Deutsch zu besuchen. Momentan ist nur die Oberfläche übersetzt, aber noch nicht der gesamte Inhalt.Wenn Sie mir bei Übersetzungen helfen wollen, ist Ihr Beitrag willkommen. Alles, was Sie tun müssen, ist, sich auf der Website zu registrieren und mir eine Nachricht zu schicken, in der Sie gebeten werden, Sie der Gruppe der Übersetzer hinzuzufügen, die Ihnen die Möglichkeit gibt, die gewünschten Seiten zu übersetzen. Ein Link am Ende jeder übersetzten Seite zeigt an, dass Sie der Übersetzer sind und einen Link zu Ihrem Profil haben.
Vielen Dank im Voraus.
Dokument erstellt 11/06/2005, zuletzt geändert 04/03/2020
Quelle des gedruckten Dokuments:https://www.gaudry.be/de/java-api-rf-org/omg/portableinterceptor/orbinitializeroperations.html
Die Infobro ist eine persönliche Seite, deren Inhalt in meiner alleinigen Verantwortung liegt. Der Text ist unter der CreativeCommons-Lizenz (BY-NC-SA) verfügbar. Weitere Informationen auf die Nutzungsbedingungen und dem Autor.
Referenzen
Diese Verweise und Links verweisen auf Dokumente, die während des Schreibens dieser Seite konsultiert wurden, oder die zusätzliche Informationen liefern können, aber die Autoren dieser Quellen können nicht für den Inhalt dieser Seite verantwortlich gemacht werden.
Der Autor Diese Website ist allein dafür verantwortlich, wie die verschiedenen Konzepte und Freiheiten, die mit den Nachschlagewerken gemacht werden, hier dargestellt werden. Denken Sie daran, dass Sie mehrere Quellinformationen austauschen müssen, um das Risiko von Fehlern zu reduzieren.