Free java application software for linux

Pylon Application Platform is a free and open source platform for embedded applications.
Our mission:
- Our goal is to dominate the world.
- We consider Microsoft as our main competitor. The second our competitor is UAZ (Ulyanovsky Automobilny Zavod) which produces UAZ vehicles. That vehicle is just another way for user to be perfect.
- Pylon is designed by programmers and for programmers only.
- Pylons authors hate Java, Java applications, and Java programmers.
- Pylons authors like Apples creatures just a little bit.
- Pylons authors love Kubuntu.
- We decline any responsibility for any results of using Pylon.
- We do not recomend to use Pylon prior to version 0.2.0-alpha1 as a platform for Nuclear Power Plant control software.
- We do not recomend to use Pylon prior to version 0.5.0 as a platform for Automatic Washing Machine firmware.
- Pylon is a way to be perfect. Nothing more
Main features:
- Pylon is absolutely free either for commercial or for any other purpose.
- It is written in pure C and C++.
- It is for Linux only.
- It is a scriptable platform. That means that Pylon-based application will be scriptable. Pylon uses Forth as a scripting language.
- Pylon-based application is supposed to be a single thread application.
- Pylon provides a non-preemptive multitasking.

Java Tools is a lightweight integrated development environment for creating, compiling, and executing Java applications and applets.
Java Tools includes point and click access to the Java files, commands, and documents. It also includes a built-in text editor and user interface for the Java debugger.
It is intended for the new Java user who needs help getting started. Its also for the more experienced Java user who wants easy access to the Java commands and a text editor.
Main features:
- GUI with built-in help and small footprint.
- Point and click access to all files (Java, manifest, HTML, image and sound) and directories (package).
- Point and click access to all commands for compiling (javac), archiving (jar), documenting (javadoc), executing (java), debugging (jdb) and disassembling (javap).
- Point and click access to all documents (Java API Specification, Java Tools and Utilities, Java Features and Java Tutorial).
- Point and click creation of all files (Java, manifest and HTML) and directories (package).
- Point and click installation of distribution archive files (Java document, Java source code, Java Tutorial and Sun Tools).
- Automatic determination of class file dependencies for archiving (jar) and documenting (javadoc) Java files.
- Checking for unused, redundant and missing imports.
- Logging of all commands invoked by GUI.
- Code metrics for Java files.
- Built-in text editor (see Edit for details).
- Built-in user interface for the Java debugger with command-line editing and history.
- Self-installing executable (Java archive file).
- Comprehensive installation and user documentation for Java and Java Tools.

Sun Java Platform Enterprise Edition (Java EE) is the industry standard for developing portable, robust, scalable, and secure server-side Java applications.

Building on the solid foundation of Java SE, Java EE provides Web services, component model, management, and communications APIs that make it the industry standard for implementing enterprise class service-oriented architecture (SOA) and Web 2.0 applications.

Secure Diary is a Java application that uses the Bouncy Castle JCE to provide strong encryption for your diary.

It stores the entries using blowfish and triple DES. It allows you to enter/view/export diary enteries in multiple diaries.

JavaSVN project is a pure Java Subversion client library. You would like to use JavaSVN when you need to access or modify Subversion repository from your Java application, be it a standalone program, plugin or web application.
Being a pure Java program, JavaSVN doesnt need any additional configuration or native binaries to work on any OS that runs Java. On this site you will also find instructions on how to make existing programs use JavaSVN instead of native javahl bindings.
Main features:
- No external binaries or libraries are needed to work with Subversion repository.
- JavaSVN supports http, https, svn and svn+ssh connection protocols.
- Low level API allows effective direct Subversion repository access.
- JavaSVN is compatible with applications that already use native javahl bindings.

tpm4java is a library for accessing trusted platform modules in your Java applications.

tpm4java runs on Linux and Windows systems and can use version 1.1b and version 1.2 TPM modules.

Java::Import::Examples is an example of how to use Java::Import to call into Java classes.

Making RMI calls from Perl

One nice thing about Java is the extremely straight forward manner in which it allows you to make calls to remote objects residing on distant servers. Many people use this ability as a point of integration between their system and a posible third party or legacy system. Unfortunatly, for the most part the ability to make calls to these remote objects is something that only other Java applications can do without making a big fuss about it. However, we can now do this from Perl.

Assume that I have a RMI server from which I can get data from in the form of simple Java Beans. One method of doing this is to use the GCJ::Cni library and natively compile and wrap a set of Java Classes which can then be used from my Perl script. However, there is an easier way.

Lets begin by descriping the Java interfaces that well be working with. We first have the Remote Interface that we will be interacting with:

import java.rmi.*;
public interface RemoteInterface extends Remote {
public SomeBean getMessage(String seedMessage) throws RemoteException;
}
And we also have the bean we will be asking for:
import java.io.*;
public class SomeBean implements Serializable {
private String value;
public SomeBean() {}
public void setValue ( String _value ) { ... }
public String getValue ( ) { ... }
}
As far as any Perl client program is concerned this is all we need to know about.
Now all there is left to do is write a client:
use Java::Import qw(
java.rmi.Naming
);

my $remote_interface = java::rmi::Naming->lookup(jstring("//localhost/Home"));
my $bean = $remote_interface->getMessage(jstring("Hi there"));
print $bean->getValue(), "n";

Thats all there is. Notice that all we had to tell Java::Import about was java.rmi.Naming, this is because it was the only class we used by name in our Perl code, every other Java class (the objects held by $bean and $remote_interface) was returned by some other method call originating from java.rmi.Naming.

In order to run this example we have to make sure everything is in its place. We start by compiling the client code. Assuming that we have been given a Stub class file (RemoteObject_Stub.class) we can do the following:

gcj -C SomeBean.java RemoteInterface.java
fastjar -cvf client.jar SomeBean.class RemoteInterface.class RemoteObject_Stub.class

Making sure our server is reachable we can then run the client code:

CLASSPATH=client.jar perl client.pl

Thats it, you should then see the message returned by your server.