Java Native Access
The developer of this repository has not created any items for sale yet. Need a bug fixed? Help with integration? A different license? Create a request here:
The definitive JNA reference (including an overview and usage details) is in the JavaDoc. Please read the overview. Questions, comments, or exploratory conversations should begin on the mailing list, although you may find it easier to find answers to already-solved problems on StackOverflow.
JNA provides Java programs easy access to native shared libraries without writing anything but Java code - no JNI or native code is required. This functionality is comparable to Windows' Platform/Invoke and Python's ctypes.
JNA allows you to call directly into native functions using natural Java method invocation. The Java call looks just like the call does in native code. Most calls require no special handling or configuration; no boilerplate or generated code is required.
JNA uses a small JNI library stub to dynamically invoke native code. The developer uses a Java interface to describe functions and structures in the target native library. This makes it quite easy to take advantage of native platform features without incurring the high overhead of configuring and building JNI code for multiple platforms. Read this more in-depth description.
While significant attention has been paid to performance, correctness and ease of use take priority.
In addition, JNA includes a platform library with many native functions already mapped as well as a set of utility interfaces that simplify native access.
JNA is a mature library with dozens of contributors and hundreds of commercial and non-commercial projects that use it. If you're using JNA, feel free to tell us about it. Include some details about your company, project name, purpose and size and tell us how you use the library.
There are also a number of examples and projects within the
contribdirectory of the JNA project itself.
JNA will build on most linux-like platforms with a reasonable set of GNU tools and a JDK. See the native Makefile for native configurations that have been built and tested. If your platform is supported by libffi, then chances are you can build JNA for it.
Pre-built platform support may be found here.
This is the core artifact of JNA and contains only the binding library and the core helper classes.
This artifact holds cross-platform mappings and mappings for a number of commonly used platform functions, including a large number of Win32 mappings as well as a set of utility classes that simplify native access. The code is tested and the utility interfaces ensure that native memory management is taken care of correctly.
See PlatformLibrary.md for details.
When posting to the mailing list, please include the following:
It's nearly impossible to indicate proper Java usage when there's no native reference to work from.
For commercial support, please contact twalljava [at] java [dot] net.
The definitive JNA reference is in the JavaDoc.
You're encouraged to contribute to JNA. Fork the code from https://github.com/java-native-access/jna and submit pull requests.
For more information on setting up a development environment see Contributing to JNA.
If you are interested in paid support, feel free to say so on the jna-users mailing list. Most simple questions will be answered on the list, but more complicated work, new features or target platforms can be negotiated with any of the JNA developers (this is how several of JNA's features came into being). You may even encounter other users with the same need and be able to cost share the new development.
This library is licensed under the LGPL, version 2.1 or later, and (from version 4.0 onward) the Apache Software License, version 2.0. Commercial license arrangements are negotiable.
NOTE: Oracle is not sponsoring this project, even though the package name (com.sun.jna) might imply otherwise.