Free java applications software for linux

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.

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.

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.

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.

Java Development Environment for Emacs (JDEE) is an Emacs-based integrated development environment (IDE) for developing Java applications and applets.
Features include multiple code browsers, a JPDA-based debugger, method and field completion, template-based and procedure-based code generation, Java source code interpreter, context-sensitive help, and more.
Enhancements:
- On XEmacs, Use efc-xemacs-query-options, i.e., a GUI dialog box instead of a text dialog box, only if use-dialog-box is nonnil.
- Fixes bug in ProjectClasses to avoid duplicate entries of imports.
- Updated JDEEs Ant interface to force use of pipes to interact with external Ant process.
- Fixed regression that caused jde-help-class-member to issue a Lisp error.
- Fixed regression in jde-wiz-update-class-list command.
- Fixed regression that caused JDEbug to issue a Lisp error when launching an application.
- Thanks to Martin Schwamberger.
- Revise the following templates to conform to CheckStyle requirements:
- jde-gen-deep-clone-template
- jde-gen-to-string-method-template
- jde-gen-bean-template
- Thanks to Martin Schwamberger.
- Added the following code generation templates:
- jde-gen-exception
- Generates an exception class in the current buffer.
- jde-gen-exception-buffer
- Generates a buffer containing an exception class.
- jde-gen-hashcode-method
- Generates a hashcode method at point.
- jde-gen-equals-method
- Generates an equals method at point.
- jde-gen-tostring-method
- Generates a toString method that uses Apaches
- ToStringBuilder class.
- Thanks to Ole Arndt.
- Enhanced jde-run-option-classpath to allow you to specify that the JDEE should omit the classpath argument when running the class or application in the current buffer, regardless of the setting of jde-global-classpath.
- Fixed regression that caused the JDEE to switch projects during debugging when stepping into code that does not belong to the project being debugged.
- Updated regular expressions used by the JDEEs interface to jdb to accommodate non-English punctuation styles for numeric expressions in debugger messages, e.g.,
- 1.200 for a line number where the English would write 1,200.
- Thanks to Morten B. Isaksen.
- In previous releases, building javadoc caused all future uses of compilation mode to try to
- display the javadoc. This release fixes the problem.
- Thanks to David Evers.
- Updated the submit-problem-report command to include an XEmacs users init.el file.

Java-Chess project is a standalone Java chess program.

Java-Chess is a fully-featured chess program that uses using Java 1.2 (including Swing) and 64-bit computing where possible.

The goal of the Java-Chess project is to develop an OpenSource chess application written in Java. We want to demonstrate that Java can be tuned to a point, where it is almost up to the performance of an application, that was directly compiled to native code.

Even clean object-oriented design does not necessarily generate an overhead, that makes high-performance computing virtually impossible.

Jada is a library useful for converting a Java application into a background daemon on Unix systems. Jada requires no rewriting of the application and is meant to be lightweight.