2 citations found. Retrieving documents...
DEC, Expersoft, HP, IBM, Netscape, Novell, Oracle, Sun, Visigenic, Xerox (1997) IDL/Java Language Mapping, Joint Revised Submission, OMG TC document orbos/97-02-01.

 Home/Search   Document Not in Database   Summary   Related Articles   Check  

This paper is cited in the following contexts:
JacORB: Implementation and Design of a Java ORB - Brose (1997)   (21 citations)  (Correct)

....section, we will first sketch the IDL language mapping used in JacORB and then focus on those points that touch on transparency. 3. 1 The Java language mapping The OMG issued an RFP for a Java language mapping in August 1996 (OMG 1996) to which there is a joint submission by all major ORB vendors (DEC et al. 1997). The final release of a corresponding specification is expected in the second quarter of 1997. Any language mapping that we might use must therefore be considered preliminary, but as the mapping is mostly straightforward, we do not expect too many changes once the OMG mapping is agreed upon. The ....

DEC, Expersoft, HP, IBM, Netscape, Novell, Oracle, Sun, Visigenic, Xerox (1997) IDL/Java Language Mapping, Joint Revised Submission, OMG TC document orbos/97-02-01.


JacORB - A Java Object Request Broker - Brose (1997)   (5 citations)  (Correct)

....one stub object in an address space for any remote object. JacORB takes care that no superfluous stubs are created or used. 3.2. 4 The Java language mapping The OMG issued an RFP for a Java language mapping in August 1996 [OMG96] to which there is a joint submission by all the major ORB vendors [Joint97]. The final release of a corresponding specification is expected in the second quarter of 1997. Any language mapping that we might use must therefore be considered preliminary, but as the mapping is mostly straightforward, we do not expect too many changes once the OMG mapping is agreed upon. For ....

....changes once the OMG mapping is agreed upon. For our purposes, we combine features from both SunSoft s and IONA s original language mappings rather than invent a complete mapping of our own here. There are, however, a number of points where our mapping differs from the proposed language mapping in [Joint97]. We will point these out in the remainder of this section. The main design rationale in our mapping is to make it natural and easy to use for Java programmers as well as easy to implement. In general, the basic IDL data types are mapped onto basic Java types, structured IDL types are mapped onto ....

[Article contains additional citation context not shown here]

DEC, Expersoft, HP, IBM, Netscape, Novell, Oracle, Sun, Visigenic, Xerox, IDL/Java Language Mapping, Joint Revised Submission, OMG TC document orbos/97-02-01, 17 February 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