Interfacing Java Clients to Legacy Applications: Lessons Learned

1998

This is a brief introduction to Java Remote Method Invocation (RMI). Java RMI is a mechanism that allows one to invoke a method on an object that exists in another address space. The other address space could be on the same machine or a different one. The RMI mechanism is basically an object-oriented RPC mechanism. CORBA is another objectoriented RPC mechanism. CORBA differs from Java RMI in a number of ways:

2001

2000

With the explosive growth of the Internet and of network services, there is a proliferation of distributed applications such as e-commerce and other web based applications that seek to leverage the power of the Internet. There have been several tools and standards for developing distributed applications including BSD sockets, RPC, and DCE. These have begun to evolve into objectbased distribution schemes such as Java Remote Method Invocation (RMI). Java RMI is increasingly being used in Internet based applications as a Java only solution to the challenges facing distributed application developers. One of these challenges includes delivering better performance to end-users. Hence it is important to study the performance parameters of RMI. This paper evaluates the performance of RMI empirically and compares its performance with the Java Sockets API. It also evaluates the benefits RMI ofsers to the developers of distributed applications. Thus Internet and web-based application developers gain an insight into the performance aspects and other tradeoffs involved when using the Java RMI distributed object architecture.

Technical White Paper, 2005

The research done in the field of object-oriented data management systems within the Global Information Systems Group has lead to a number of implementations of the Object Model (OM) data model. The family of Object Model System (OMS) implementations comprises platforms implemented in Prolog, Java and C++. Rapid prototyping with these systems can only be achieved, if it is possible to move freely from one system to another. Therefore all implementations of the OM model share a common language for data definition, manipulation and querying. As OM standardises the way data is represented, the Object Model Language (OML) standardises the way in which to interact with data. What is missing is an Application Programming Interface (API) that defines how programmes can work with an OMS database.

ACM SIGPLAN Notices, 1998

Java has an important role in building distributed object oriented web enabled applications. In the article an analysis of two distributed object models in context of Java language is presented. Several aspects of RMI and CORBA such as features, maturity, support for legacy systems, learning curve and ease of development are compared. A special emphasis is given to the performances. Different testing scenarios give a complete overview about real world performances of both architectures. Based on the comparison results, recommendations for selecting the most appropriate architecture for a given problem domain are presented. Therefore the paper contributes to the understanding of the distributed object architectures and to the study of Java RMI and CORBA performances.

2001

"In this paper, we present the main objectives and components of the OMS Java data management framework. We argue that developers of modern information systems require high-level application programming interfaces, storage platform independence and support for universal client access. We describe how the OMS Java framework provides three level of abstractions – storage, information and access in order to realise these objectives. We then present each of these layers in turn – starting with the information abstractions which lie at the core of the system and then going on to the storage and access layers."

Proceedings of the ninth annual conference on Object-oriented programming systems, language, and applications - OOPSLA '94, 1994

The panel will discuss emerging "industrial" solutions that help programmers to develop distributed and client/server applications based on objects supporting so-called openness and heterogeneity. The goal of the panel is to help answer the question whether there can be one single solution or whether various (integrated) approaches are needed. The panel will also compare industrial solutions such as COM, DSOM, CORBA and OODCE with results that came out of academia. Finally, a set of questions will be answered by each panelist according to the approach he will propose.

An important aspect of research on software objects, components, and component-based applications concerns their interoperation. Is their interoperation technically possible? Which elements are responsible for the software objects' incompatibility? Is compatibility a responsibility of the objects or of their underlying architectures? In this article we discuss the object compatibility problems, we describe basic strategies for bridging the gap between the three basic middleware remoting technologies (CORBA, DCOM, and RMI), and present ...

2001

An important aspect of research on software objects, components, and component-based applications concerns their interoperation. When there is a need for two or more software components, based on different technologies, to interoperate the mission target is to make the components hide the fact that the other components are functioning under a different technology without changing their characteristics and behavior. In this paper we describe basic strategies for bridging the gap between the three basic middleware remoting technologies (CORBA, DCOM, and RMI) and present our approach for a Java-based Object Mediator architecture.

2000