Sun Microsystems. Java native interface specification, 1997.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....compiler vendors provide their own in house interfaces to other languages, in particular C. Within the current standardization effort for Fortran 200x a Fortran C interface will be defined [118] Java, on the other hand, has defined a sophisticated interface to C, the Java Native Interface (JNI) [173]. Therefore, interoperability between Fortran and Java is best accomplished via C. More specifically, any data passed from Fortran to Java is converted to an appropriate C data type according to the type mapping defined by the employed compiler or by the upcoming standard and eventually converted ....

SUN Microsystems. Java Native Interface Specification, 1997.

....up management into three different levels: a) an instrumentation level, b) an agent level, and c) a manager level. On a) we find management instrumentation, i.e. management interfaces of arbitrary Java objects. Management of non Java resources can be achieved via the Java Native Interface (JNI, [21]) Instrumentation is encapsulated by so called management beans (MBeans) On the agent level (b) JMX proposes MBean servers that are container objects providing a certain runtime environment for MBeans. MBean servers use protocol adapters to allow manipulation of MBeans by various manager ....

Sun Microsystems Inc. Java Native Interface Specification. http: //java.sun.com/products/jdk/1.2/docs/guide/jni/spec/ jniTOC.doc.html, May 1997. REFERENCES 22

....were developed. There are, for example, products such as JPVM [8] jPVM (formerly JavaPVM) 9] JavaMPI [7] HPJava [6] or DOGMA [3] which aim at enabling parallel and distributed programming with Java. While jPVM accesses the original PVM implementation via the Java Native Interface (JNI) [18], JPVM is a purely Java based solution developed from scratch. A detailed description of JPVM and an assessment of its performance can be found in [4] and [20] In this paper, we focus on CORBA as a potential middleware solution for distributed parallel programming and we present our approach to ....

Sun Microsystems Inc. (1997): "Java Native Interface Specification"; JDK 1.1, May 16, 1997, http://java.sun. com/products/jdk/1.2/docs/guide/jni/spec/jniTOC.doc. html

....parallel and distributed programming with Java, such as JPVM [8] jPVM (formerly JavaPVM) 9] JavaMPI [7] HPJava [6] or DOGMA [1] gives evidence of the need for this kind of solutions in the Java world. While jPVM accesses the original PVM implementation via the Java Native Interface (JNI) [19], JPVM is a purely Javabased solution developed from scratch. A detailed description of JPVM and an assessment of its performance can be found in [4] and [21] However, in the CORBA environment there is still a lack of simple language and platform independent approaches to the problems of ....

Sun Microsystems Inc. (1997): "Java Native Interface Specification"; JDK 1.1, May 16, 1997, http://java.sun. com/products/jdk/1.2/docs/guide/jni/spec/jniTOC.doc. html

....were developed. There are, for example, products such as JPVM [7] jPVM (formerly JavaPVM) 8] JavaMPI [6] HPJava [5] or DOGMA [1] which aim at enabling parallel and distributed programming with Java. While jPVM accesses the original PVM implementation via the Java Native Interface (JNI) [16], JPVM is a purely Java based solution. A detailed description of JPVM and an assessment of its performance can be found in [3] and [18] In this paper, we focus on CORBA as a potential middleware solution for distributed parallel programming and we present ways of modeling and implementing ....

Sun Microsystems Inc. (1997): "Java Native Interface Specification"; JDK 1.1, May 16, 1997, http://java.sun. com/products/jdk/1.2/docs/guide/jni/spec/jniTOC.doc. html

....were developed. There are, for example, products such as JPVM [7] jPVM (formerly JavaPVM) 8] JavaMPI [6] HPJava [5] or DOGMA [2] which aim at enabling parallel and distributed programming with Java. While jPVM accesses the original PVM implementation via the Java Native Interface (JNI) [17], JPVM is a purely Java based solution developed from scratch. A detailed description of JPVM and an assessment of its performance can be found in [3] and [19] In this paper, we focus on CORBA as a potential middleware solution for distributed parallel programming and we present our approach to ....

Sun Microsystems Inc. (1997): "Java Native Interface Specification"; JDK 1.1, May 16, 1997, http://java.sun.com/products/jdk/1.2/docs/guide/jni/spec/ jniTOC.doc.html

....applications (compatibility) portability of source code, performance, and . scalability. For a Java based application, there are four possible technologies on which communication with the SAP R 3 System can be based: Remote Method Invocation (RMI) 23] Java Native Interface (JNI) [22], Distributed Component Object Model (DCOM) 6] Common Object Request Broker Architecture (CORBA) 7] Since version 1.1, RMI has been shipped together with the Java Development Kit (JDK) and therefore has been made available to all users of a JDKcompliant development environment. The ....

Sun Microsystems Inc. (1997): "Java Native Interface Specification"; JDK 1.1, May 16, 1997, http://java.sun.com/products/jdk/1.2/docs/guide/jni/ spec/jniTOC.doc.html

....(compatibility) portability of source code, performance, and . scalability. For a Java based application, there are four possible technologies on which communication with the SAP R 3 System can be based: Sun s Remote Method Invocation (RMI) 18] Sun s Java Native Interface (JNI) [17], Microsoft s Distributed Component Object Model (DCOM) 6] OMG s Common Object Request Broker Architecture (CORBA) 7] Since version 1.1, Sun s RMI has been shipped together with the Java Development Kit (JDK) and therefore has been made available to all users of a JDK compliant ....

Sun Microsystems Inc. (1997): "Java Native Interface Specification"; JDK 1.1, May 16, 1997, http://java.sun.com/products/jdk/1.2/docs/guide/jni/ spec/jniTOC.doc.html

....were developed. There are, for example, products such as JPVM [9] jPVM (formerly JavaPVM) 10] JavaMPI [8] HPJava [7] or DOGMA [2] which aim at enabling parallel and distributed programming with Java. While jPVM accesses the original PVM implementation via the Java Native Interface (JNI) [19], JPVM is a purely Java based solution developed from scratch. A detailed description of JPVM and an assessment of its performance can be found in [5] and [21] In this paper, we focus on CORBA as a potential middleware solution for distributed parallel programming and we present ways of ....

Sun Microsystems Inc. (1997): "Java Native Interface Specification"; JDK 1.1, May 16, 1997, http://java.sun. com/products/jdk/1.2/docs/guide/jni/spec/jniTOC.doc. html

....make use of lowlevel system functionality through the use of native methods, which are written in a language such as C. To bind native method code to the Java application, a native method interface is used, which has been standardized across most JVMs as Sun Microsystems Java Native Interface [29]. However, the use of native methods raises two important concerns. The first is performance: the cost of traversing the native method interface can be quite high, especially when a large amount of data must be transferred across the Java native code boundary. The second is safety: invoking ....

....operating systems. The garbage collector is based on Boehm s incremental copying collector [3] Many standard Java libraries are supported, and the runtime includes a Java bytecode interpreter for executing dynamically loaded classes. GCJ supports two native code interfaces: Sun Microsystems JNI [29], as well as the Cygnus Native Interface (CNI) 26] an e#cient Java binding to C . The Jaguar front end compiler takes a Java classfile and produces a Jaguar classfile containing Jaguar bytecode (which may be the same as the Java bytecode, if no translation rules were applied) The Jaguar ....

Sun Microsystems Inc. Java Native Interface Specification. http://java.sun.com/products /jdk/1.2/docs/guide/jni/index.html.

....make use of low level system functionality through the use of native methods, which are written in a language such as C. To bind native method code to the Java application, a native method interface is used, which has been standardized across most JVMs as Sun Microsystems Java Native Interface [21]. However, the use of native methods raises two important concerns. The first is performance: the cost of traversing the native method interface can be quite high, especially when a large amount of data must be copied across the Java native code boundary. The second is safety: invoking arbitrary ....

Sun Microsystems Inc. Java Native Interface Specification. http://java.sun. com/products/jdk/1.2/docs/guide/jni/index.html.

....in a C function. In order for the Java application to invoke this C function, the original JOQL query (embedded in the Java application) is replaced with Java code that invokes the generated C function. Finally, the toolset automatically applies the Java Native Interface (JNI) mechanism [8] in order to generate an interoperability bridge between the Java application and the generated C OQL code. To gain a better understanding of the internal operation of the Query Translator, consider a C OODB that is populated with instances of the Car class. Suppose a software developer is ....

Sun Microsystems, Inc. (Cupertino, CA). Java Native Interface Specification, 1997. http://java.sun.com/products/jdk/1.1/docs/guide/jni/spec/jniTOC.doc.html.

....multiple mobile code systems, which can coexist within a node. The current PAN implementation supports both a simple (and completely insecure) system for dynamically loading Intel ix86 object code and an interface to any Java Virtual Machine [19] that supports the Java Native Interface (JNI) [20]. Java is supported currently only in userspace nodes due to the lack of an in kernel JavaVM; work is in progress on making the Kaffe OpenVM JavaVM work inside the kernel. C. PAN interfaces The PAN Node Interface (PNI) presents code objects, and hence capsules, with a uniform interface to data ....

Sun Microsystems, Mountain View, CA, Java Native Interface Specification, Release 1.1 edition, May 1997.

....via Sockets. Another sockets based implementation used Java sockets on both the client and the server. The Java Native Interface (JNI) was then used to inter operate with C . The JNI is a technique that allows Java to communicate via shared libraries with programs written in either C or C [13]. Figure 4.2 shows this alternative sockets implementation. Java C J N I Sockets Java 000 000 000 000 000 000 000 000 000 111 111 111 111 111 111 111 111 111 CLIENT SERVER Figure 4.2: Java to Java via Sockets to C via JNI. The pseudo code representation of the sockets based clients is ....

....4 introduced the JNI. The JNI provides the mechanism by which the Java half of the Distributed GUI Server communicates with the C half and thereby Carmen itself. The JNI essentially provides an interface pointer which accesses a lookup table. This arrangement is represented in Figure 6. 1 [13]. To use the JNI shared libraries need to be created that are dynamically loaded by the JVM. Once these libraries have been loaded, calls can be made to and from C (or C) as desired. Interface Pointer Pointer Pointer Pointer Pointer interface function interface function interface ....

Sun Microsystems. Java native interface specification. http://java.sun.com/products/jdk/1.1/docs/guide/jni/spec/jniTOC.doc.html, May 1997.

No context found.

Sun Microsystems. Java native interface specification, 1997.

No context found.

Sun Microsystems, Inc -- "Java Native Interface Specification", available at http://java.sun.com/products/jdk/1.2/docs/guide/jni/spec/jn iTOC.doc.html (April/16/2002.

No context found.

Sun Microsystems. Java Native Interface specification. http://java.sun.com/j2se/1.3/docs/guide/jni/spec/jniTOC.doc.html, 1997.

No context found.

Sun Microsystems. Java Native Interface Specification, May 1997. http://java.sun.com/ j2se/1.4/docs/guide/jni/.

No context found.

Sun Microsystems, Inc " Java Native Interface Specification" Sun Microsystems, Inc, March 1997 http://java.sun.com/products/jdk/1.1/docs/guide/jni/spec

No context found.

). Sun Microsystems. 1997. Java native interface specification. http://java.sun.com/products/jdk/1.2/docs/guide/jni/spec/jniTOC.doc.html (Accessed 24 November 1998). Teitelbaum B., and Ted Hanss. 1998. QoS requirements for Internet2 (draft) http://www.internet2.edu/qos/may98Workshop/html/requirements.html (Accessed

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