Free java to exe software for linux

Java Tetris project is a simple Tetris game.
Java Tetris is a game written with Eclipse and the VE Plugin. It is a nice starting point if you want to learn Java and Eclipse.
The game can be started as Java applet or Java application.
Enhancements:
- The dependency on jdom was removed.
- The jar is now only 30kb.
- A bug was fixed in the score list.

Java Sudoku is a cross platform version of the popular Sudoku logic game. Java Sudoku features an advanced user interface that is both easy to use and appealing to the eye.
It allows you to generate completely random Sudoku puzzles, enter your own puzzles from newspapers and magazines, or load them from Sudoku XML files. Java Sudoku can also be used as a Sudoku generator and solver.
Main features:
- Random puzzles every time you play
- Helping lines mode in the option menu, so You can see easier, if there is a collision
- 2 different systems of selecting cells and entering numbers
- 3 difficulty levels and an user custom level
- 3 Different Numbers Distributions
- Load/Save Sudoku games without any kind of losses
- Design your own puzzles - Under construction

Java Web Shell is a web based interactive shell-type environment written in Java.

Obviously, to use the shell, youll need to be using a browser that supports Java Applets, and this has been compiled using the Sun 1.4.1 JDK.

Head over to Sun and pick up the latest runtime enviroment if you dont already have it.

Java GetOpt library implements option parsing and a common online help behaviour, including an XML format for topics, command, and options (which can be queried with --help --xml) and support for online browsing with --help --browse.

Whats New in This Release:

ï¿1⁄2 The getopt library can now choose the pluggable look and feel of an application with a standard option "--plaf".
ï¿1⁄2 A new file of default options (.prefs/default.options) can specify a set of common default options for all programs using the getopt library, such as the PLAF.

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::SJ is a highly configurable Java program startup system.

SYNOPSIS

sj myprogram.sj

This module allows you to very easily run Java services that rely on complex configuration at the VM and library level. It also provides an easy way of specifying a sensible default configuration that can be overridden by specific applications should they need to.

The system is configured on a machine and application level. The system looks for configuration files in a set of well-known locations, currently these are:

/etc/sj.conf
.sj.conf in users HOME directory
.sj.conf in current working directory

Every application is defined in terms of a similar configuration file. The configuration system has been designed so that it is easy to write a simple and minimal configuration file for a program.
Provided the system has a fairly complete configuration associated with it then an application configuration file need only have the class name to be executed.

The Java Gui Builder program is designed to decouple the GUI building code from the rest of the application code, without hand-writing code.

It allows one to describe the layout of windows and controls using an XML file. A full DTD was written to allow on-the-fly validation.

Using an XML file to describe GUI components allows users the flexibility to rewrite their windows so that they suit their needs, without opening up the innards of the program to the users.

Java Gui Builder can run on any Swing enabled J2SE platform. JGB was tested against Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_08-b03) and Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_01-b01). If you want to build JGB, you will need J2SE 1.4 or better. It is not possible to build on 1.3, but can be used on 1.3.