Free java based software for linux

Java Embedded Python embeds CPython in Java. It is safe to use in a heavily threaded environment, it is quite fast and its stability is a main feature and goal.
Main features:
- Using the native Python interpreter may mean a massive speed improvement over Java-based languages.
- Python is mature so authors neednt fear the interpreter will suddenly change widely-used features.
- Access to the high quality Python modules, both native and Python-based.
- Compilers and assorted Python tools are as mature as the language.
- Python is an ideal language for your business logic. It is easy to learn, eminently readable and generally immune to programming gotchas.
Patches, comments and other help is greatly appreciated. If you need help, post to the SourceForge mailing list or forums. Please include code snippets for the most accurate response.

Java::JCR is a module to use JSR 170 (JCR) repositories from Perl.

SYNOPSIS

use Java::JCR;
use Java::JCR::Jackrabbit;

my $repository = Java::JCR::Jackrabbit->new;
my $session = $repository->login(
Java::JCR::SimpleCredentials->new(username, password)
);

my $root = $session->get_root_node;
my $node = $root->add_node(foo, nt:unstructured);
$node->set_property(bar, 10);
$node->set_property(baz, blah);
$node->set_property(qux, 4.8);
$session->save;

The JSR 170 specification describes a Java-based API for access hierarchical databases. This is generally referred to by the abbreviation JCR, which is an abbreviation for Content Repository API for Java Technology Specification.

The biggest OSS implementation, as of this writing, is Jackrabbit, which is a project at the Apache Software Foundation, http://jackrabbit.apache.org/. Currently, this library allows Perl programmers to develop using the JCR and Jackrabbit, though, theres no reason why connectors cant be written for other implementations, such as Jaceira, CRX, eXoplatform, etc. The JCR library wrappers included are not at all specific to Jackrabbit.

Java Classic RPG is an RPG framework, engine, and game that uses OpenGL, a challenging AI, huge territories, and classic pen-and-paper turn-based combat. This project is in the tradition of games like Wizardry 7 and EOB, but incorporates innovations made possible by modern computing technology.
The framework and engine feature a self-containing, playable, algorithmically-generated world, and can be the base for new games.
Enhancements:
- The 3D core was refactored, a new jungle design (along with partly billboarded trees and bushes) was added, and several optimizations and bugfixes have been included.

Jagzilla is simply the Java version of bugzilla. The idea of this project is:
- To provide a complete java-based interface to bugzilla
- To facilitate interoperation between bugzilla and java based apps
- To provide additional functionality to bugzilla while mantaining compatibility
Main features:
- Bugzilla and java based apps integration
- Bugzilla and eclipse integration (with the eclipse plugin)
- Bugzilla and cvs integration (with the eclipse plugin)
- Bugzilla extended functionality mantaining backwards compatibility (with jagzilla extension tables)
Components:
Hibernate Mapping
- This components includes java classes that represent rows in bugzilla tables, as well as mapping files. This provides direct hibernate access to bugzilla database.
Jagzilla Core API
- The core api is a higher abstraction level than hibernate mapping, which understands buisiness logic and provides an easy access to this funcionality.
Jagzilla Web Services API
- The web services API is actually the core api implementation which uses xml and http as transport. see rest-webapp
WS Client lib
- This is a simple jar to enable easy access to jagzilla WS from any java app.
Jagzilla mail processor
- A program to read email accounts and add bugs to database with information found on these mails.
Hibernate Client lib
- This is a simple jar to enable easy access to jagzilla Core API from any java app.
Eclipse plugin
- This plugin enables using most functionallity of jagzilla. The access can be with hibernate and JDBC (directly to the database) or via web services.
Webapp
- This is the web frontend for jagzilla. This web application shows how to use the jagzilla backend to provide a java web based front-end.
REST Webapp
- This web application is the server for the web services (in a simple sense of xml over http) interface.

Java DIME Library project implements Direct Internet Message Encapsulation (DIME), which is a lightweight binary encapsulation format that can be used to encapsulate multiple payloads of arbitrary types and sizes into a single message.
DIME is ideal for incorporating binary attachments into any XML-based protocol. The library fully supports the latest DIME specifications.
Enhancements:
- Corrected DimeRecord.isFirst() thanks to John Russell

avalon-harvest provides an Avalon-based integration package.
Harvest is a very simple Java-based program to asynchronously copy data from one location to another.
The data can be anything that can be represented as a Java bean, for example, files or database records.
Data can be anything, including files, database records, data available from networks, JMS messages, or whatever you can imagine and represent as java bean.
Main features:
- Assynchronious system integration, where no other solution exists.
- Data replication between databases
- Fetching data from unusable datasources (html pages, documents, other files) into database (or any kind of device capable of storing data)
- Any other scenarios where you may need assynchronious copy of data.

Construct is a framework for command processing. It is based on a request/response cycle managed by a Controller. Construct-java has support for filters, filter chains and command chaining. The controller has two modes for request processing: synchronous and asynchronous. Validators (commons-validator) are also supported.
Main features:
- Synchronous/Asynchronous request procesing
- Command chaining (Chain of Responsability)
- Apply filters before and after request processing
- Commons-validator support
- Spring integration
Enhancements:
- Open source release to java.net.

Java::Build::GenericBuild is a high level driver to control Java builds.

SYNOPSIS

There are two (or more) code files needed to effectively use this module. First, create a subclass of this class:

package Java::Build::MyBuild;
use Carp;

# Do the following in a BEGIN block before the use base statement:
BEGIN { $ENV{CLASSPATH} .= ":/path/to/suns/lib/tools.jar"; }
use base Java::Build::GenericBuild;
# use any other Java::Build modules you need

my @args = (
{ BUILD_SUCCESS => sub { croak "You must supply a BUILD_SUCCESS" } },
{ CONFIG_LOC => sub { croak "You must supply a CONFIG_LOC" } },
{ MAIN_DIR => &_form_main_dir },
# ...
); # Include all the attributes that matter to your build here, and
# what to do if the caller omits them.
# If they are required, die in the subroutine, otherwise provide a
# subroutine reference which will fill in the default

sub new {
my $class = shift;
my $self = shift;
$self->{ATTRIBUTES} = @attrs;
process_attrs($self);

return bless $self, $class;
}

# Include common targets callers can share here. Put unique targets
# in the calling scripts (see below).
sub init { my $self = shift; ... }
sub cvs_refresh { my $self = shift; ... }
sub compile { ... }
# ...
sub _form_main_dir { my $self = shift; $self->{MAIN_DIR} = /usr/src; }
In some script:
#!/usr/bin/perl
use strict; use warnings;

use Java::Build::MyBuild;

my $project = Java::Build::MyBuild->new(
BUILD_SUCCESS => /where/this/module/can/store/build/state.info,
CONFIG_LOC => /some/path/to/my.conf,
NAME => MyApplication,
SRC_DIR => /where/my/java/files/live,
SUBPROJECTS => [
{ NAME => "util" },
{ NAME => "app", USING => &compile_app },
],
);
$project->targets(qw( init cvs_refresh unique compile ));
$project->GO(@ARGV);

package Java::Build::MyBuild; # re-enter the build package to add targets
sub unique {...} # a routine that MyBuild doesnt provide