49 results about "Java Native Interface" patented technology

A method and apparatus for transforming JAVA Native Interface function calls to constants, internal just-in-time (JIT) compiler operations or simpler intermediate representation. A compiler generates a plurality of intermediate representations for a plurality of native interface function calls. During inlining of native code, matching is performed on each native function call (against this list) and a list of native interface function calls is generated. For each native interface function call, a (JIT) call transformer attempts to replace the native interface function call with a constant, internal JIT compiler operation or a simpler intermediate representation depending on the type of native interface function call.

A method of integrating an Xt Intrinsics based toolkit with a JAVA application. The application includes a process thread that implements an X event loop and an application thread that suspends execution of the event loop to allow a call to be made through the JAVA Native Interface to a toolkit or a widget to cause something to be displayed. The application thread includes a write socket to communicate a token to a read socket of the event loop, and performs a blocking read suspending the thread. The event loop returns an acknowledgment token via a write socket to a read socket of the thread that unblocks its blocking read and the event loop invokes its own blocking read suspending its execution. The file descriptor function, XtAppAddInput, preferably, is used to read the token and to set the blocking read. After a toolkit call is made, a token is sent from a second write socket of the thread to a second read socket of the event loop that unblocks its blocking read resuming the event loop. JAVA multithreading support services, such as JAVA's wait and notifyAll methods, are employed in multithreaded applications to ensure that only one thread at a time can make a call. Use of a separate Intrinsics application context to service the event loop is employed, windows are managed in separate hierarchies associated with each application context, and a special JAVA Canvas manages native windows transparent to the programmer.

This invention is directed to a method and apparatus for implementing native code directly in C++ with object structure very closely resembling the object structure of JAVA. The method provides for the mapping of JAVA to C++ objects and invoking the JAVA Native Interface, mapping C++ objects to JAVA and returning a corresponding JAVA object, retrieving and returning a class factory by class name, and collecting garbage in both the C++ and JAVA environments.