12 citations found. Retrieving documents...
OMG (Object Management Group). The CORBA/IIOP 2.2 Specification. OMG Document formal/98-02-01, 1998.

 Home/Search   Document Not in Database   Summary   Related Articles   Check  

This paper is cited in the following contexts:
Support for Design Patterns through Graph Transformation Tools - Radermacher (1998)   (4 citations)  (Correct)

....project (funded by the BMBF) includes two industrial partners (Aachener and Mnchener insurance company and the GEZ an institution charging TV fees) The project aimed at tools supporting the distribution of monolithic applications. The resulting application should employ a middleware like CORBA [OMG98] or DCOM [Ses97] We divided this task in two subgoals: 1) transformation towards an object based structure (if not already existent) and (2) distribution of the application. The latter implies a restructuring of the application to meet certain prerequisites of the middleware, for example the ....

OMG (Object Management Group). The CORBA/IIOP 2.2 Specification. OMG Document formal/98-02-01, 1998.


DiTo - A Distribution Tool Based on Graph Rewriting - Radermacher (2000)   (2 citations)  (Correct)

....We present two sample sessions demonstrating the use of DITO. The first is the simple information system we have already seen in the paper. The second is the Java part of DITO itself. 1 Introduction Consider the task of developing a distributed application on top of a middleware like CORBA [OMG98] or DCOM [Ses97] If a monolithic variant of such an application already exists, it is necessary to restructure this application in order to meet certain prerequisites of the middleware, for example the indirection of remote object instantiation via a factory. The main goal is the creation of a ....

OMG (Object Management Group). The CORBA/IIOP 2.2 Specification. OMG Document formal/98-02-01, 1998.


An Architectural View of Distributed Objects and Components in .. - Plasil, Stal (1998)   (4 citations)  (Correct)

....(e.g. in Orbix) where the client stubs directly communicate with a POA. The Interface Repository is used for introspection (particularly in case of a dynamic invocation and dynamic delivery) The Implementation Repository is used for reactivation of servers. The CORBA Lifecycle Service [9] employs the Abstract Factory pattern: In addition to a classical factory, the Lifecycle Service defines also factory finder (returns an object factory able to create object of a given type) and generic factory (which encapsulates the functionality of multiple factories) 3.3 Providing and ....

OMG: CORBAservices Specification, Lifecycle Service, OMG document FORMAL/97-2-11, OMG 1997


Additional Structuring Mechanisms for the OTS Specification - International Business..   (Correct)

....interfaces for the coordination and control of activities. Some of these activities may be transactional, and others may be transactional for only specific periods of time. When transactions are used, this specification requires them to be provided by the OMG s Object Transaction Service (OTS) [3]. 1.2.2 OTS Compatibility This proposal does not require any changes to the Object Transaction Service. 1.2.3 Additional Functionality This proposal does not require any additional functionality from any adopted OMG specifications. 1.3 Satisfaction of Optional Requirements This submission ....

OMG, CORBAservices: Common Object Services Specification, Updated July 1997, OMG document formal/97-07-04.


Additional Structuring Mechanisms for the OTS Specification - International Business..   (Correct)

....specification, so there are no inherent restrictions on scalability. 1. 5 Relationship to Existing OMG Specifications The Activity Service specification is directly based upon the following OMG technology: OMG CORBA Object Request Broker (ORB) 1] OMG Interface Definition Language (IDL) [2]. OMG Object Transaction Service (OTS) It is anticipated that the Activity Service will aid, if desired, the deployment of the following OMG technologies: OMG Workflow Management Facility. The Activity Service specification requires the addition of the following System Exceptions to the ....

OMG, The Common Object Request Broker: Architecture and Specification, Revision 2.1, August 1997, OMG document formal/97-0901.


Object Management Group - Framingham Corporate Center   (Correct)

No context found.

CORBAservices: Common Object Services Specification, Revised Edition, March 1995. OMG Document formal/97-05-03.


Object Management Group - Framingham Corporate Center   (Correct)

No context found.

CORBAservices: Common Object Services Specification, Revised Edition, March 1995. OMG Document formal/97-05-03.


Object Management Group - Framingham Corporate Center   (Correct)

No context found.

CORBAservices: Common Object Services Specification, Revised Edition, March 1995. OMG Document formal/97-05-03.


Object Management Group - Framingham Corporate Center   (Correct)

No context found.

CORBAservices: Common Object Services Specification, Revised Edition, March 1995. OMG Document formal/97-05-03.


Object Management Group - Framingham Corporate Center   (Correct)

No context found.

CORBAservices: Common Object Services Specification, Revised Edition, March 1995. OMG Document formal/97-05-03.


Object Management Group - Framingham Corporate Center   (Correct)

No context found.

CORBAservices: Common Object Services Specification, Revised Edition, March 1995. OMG Document formal/97-05-03.


Persistence in CORBA - Tuma (1997)   (Correct)

No context found.

OMG97J CORBAservices Specification, Full Book, OMG document FORMAL/97-6-1, ftp://ftp.omg.org, 1997.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC