Netx Version 0.5
An open-source JNLP client
Join our mailing lists!

Must be willing to write quality code / docs.
If you include netx as part of your application please use one of these logos:

Under construction.
About Netx - NETwork eXecute
Netx is a high-quality implementation of the Java Network Launching Protocol (JNLP). It downloads code over the network for applications and applets, caches it, and runs it in a secure environment.

General Features of netx and JNLP:
  • Quality: Highest quality open-source JNLP client.
  • Modular: Easily add JNLP capabilities to any applications.
  • Security: Run code in a sandbox or log its activities.
  • Small Size: Loads from a ~130K JAR file.
  • Auto-Update: No special code needed to auto-update apps.
  • Fast startup: Runs code from a cache for fast starting.
  • Saves Memory: Supports running apps in a shared JVM.
  • No Browser: Runs apps and applets without a browser.
  • Web Based: No installers needed to deploy an application.

Netx was designed from the ground-up to be a library for adding JNLP features to other applications. This allows the API to be clean, simple, and easy to use.  Netx avoids the bloat and complication from application browsers and other UIs because these are done by other apps such as the Java Start button and OCD/Xito.
What is JNLP?
The Java Network Launching Protocol describes internet applications and applets, what resources they need, and how to run the code. The basic idea of JNLP is to let a user click on a link and have an application or applet run outside the browser.

The idea behind the JNLP protocol is to enable users to click a link in their web browser and have an internet-based application run outside the browser - like a super applet. Users get the advantage of HTML-based applications (always up-to-date, no installing or configuring, "instant-on", etc) and also the advantages of a traditional application.

Everything in JNLP revolves around a ".jnlp" file. These are XML files that describe an application or applet, and the resources needed to be cached in order to run them locally. It includes security requirements, meta-data such as vendor and icons, and other information.
Written by Jon A. Maxwell (JAM)


Deane Richan, Graham Heyes, Thomas Singer, Steve Menard, Jan Boesenberg, Karsten Lentzsch, Scott Pennell, and others.