Free jdk software for linux

JDraw is a pixel oriented graphics editor designed especially for small to medium-sized pictures used to decorate web pages.
JDraw image editor is completely written in Java, simple to use and saves (animated) GIFs, ICOs and PNGs.
I started writing this tool because it took me ages to do little things like changing a couple of pixels, making a colour transparent, adjusting some RGB values. Most graphic tools irritate with hundreds of sexy filters but have steep learning curves or just dont care about simple pixels.
So its high time for a good old pixel editor.
Programming language: JDraw is entirely written in Java. Originally written for JDK 1.4 it now supports JDK 1.3 as well.
Supported Platforms: So far I developed and tested JDraw under Windows XP and SuSe Linux 8.1.
Main features:
- plain, filled and gradient filled rectangles
- plain, filled and gradient filled ovals
- plain and gradient filled text
- colour picking, cropping, filling
- image scaling (since v1.2beta)
- image rotation (since v1.2.1beta)
- copying/moving clips
- rotating/flipping clips (since v1.2.2beta)
- save animated GIFs (interlaced/not interlaced)
- save PNGs (interlaced/not interlaced)
- save ICOs (true colour, 32 bit) (since v1.1.3)
- save JPEGs of configurable quality (since v1.1.4)
- read all image formats supported by Java
- colour reduction, colour replacing, colour swapping
- grayscaling (since v1.2.2beta)
- image browser (since v1.3beta)
- tolerant fill tool (since v1.3beta)
- palette operations like editing RGB colours, alpha values
- configuration of the Look&Feel to use (since v.1.1.3)

JAMWiki is a Java-based Wiki engine.
JAMWiki features Java servlet 2.3 and JDK 1.4 compatibility, feature parity with MediaWiki, quick and easy setup, and support for running either with or without an external database.
Enhancements:
- This is a minor release that includes some new features as well as bugfixes.
- Notable changes made during this release include updates to the wiki syntax parser, an upgrade to the Spring Framework version 2.0.4, an upgrade to Lucene Search Engine version 2.1, and a new Special:Listusers page to provide a list of all registered wiki users.

JVending project bridges P2P networks and wireless delivery of content to mobile devices. Due to high latency of wireless connections, it is not practical to directly hook up the mobile devices to the peer network, so I have taken a different approach with JVending.

A user sets up a personal provisioning server on their PC and hooks it into the network. Through the P2P network, we create a federation of provisioning servers. The mobile devices use the federated provisioning servers as content portals.

JVending differs from P2P systems, such as Gnutella or "Project JXTA" reference implementation, in the following ways. JVending provides:

1. Catalog management
2. Device detection, which delivers the appropriate content based upon the type of browser or device
3. Web based browsing of content, so you can share with your friends on a wired or wireless network, after you have already collected the content.
4. The ability to search for and distribute packaged archives on the peer network.
5. Web links tying together the network.
6. PPG integration for pushing content to mobile devices.

For 2005 - 2006, the major goals of JVending (roughly in order of importance) are:

1. Expanding P2P support, including more in the area of wireless messaging (SMS)
2. JSR-124 compliance
3. Performance testing and monitoring capability
4. Multimedia server and J2ME support. This covers full integration between the MMS Client and the provisioning server.

Setting up the Environment

Follow these steps:

1. Make sure that you have J2SE 1.4.2 JDK installed. If not, go to http://java.sun.com/j2se/1.4.2/download.html and download and install the JDK (not JRE). I have not tested with J2SE 1.5 JDK, so it may or may not work with that version.
2. Download the jvending-standalone.zip file from the JVending project site.
3. Unzip the file into a directory of your choice, say /jvending
4. Set the JAVA_HOME environmental variable, depending on your OS. In windows, you can do this through the Control Panel/System/Advanced/Environmental Variable: JAVA_HOME =
EXAMPLE: JAVA_HOME=c:Programsj2sdk1.4.2_06

Starting JVending

1. Go to the bin directory and click on the run.bat (for windows) or run.sh for Unix.
2. The first time you start JVending, you will see a JXTA Configurator screen show up. Type in your user name and password/verify password. Click OK.
3. Wait 10 seconds for JVending to finish its startup sequence and then go to http://localhost:80/jvending/login. If you get a 404 error, wait a few more seconds and try again. Login ID/Password: admin/admin. Click "Submit Query" button. You will now see the JVending home page.

Dozer project is a powerful, yet simple Java Bean to Java Bean mapper that recursively copies data from one object to another. Typically, these Java Beans will be of different complex types.
Dozer supports simple property mapping, complex type mapping, bi-directional mapping, implicit-explicit mapping, as well as recursive mapping. This includes mapping collection attributes that also need mapping at the element level.
Dozer not only supports mapping between attribute names, but also converting between types. Many conversion scenarios are supported out of the box, but Dozer also allows you to specify custom conversions via XML.
The mapper is used any time you need to take one type of Java Bean and map it to another type of Java Bean. Most field mapping can be done automatically by Dozer using reflection, but any custom mapping can be predescribed in XML format. Mapping is bi-directional so only one relationship between classes needs defining. If any property names on both objects are the same you do not even need to do any explicit property mapping for these fields.
The picture below depicts some of the common areas for Dozer to be inserted into an architecture. Notice that it typically is utilized at the boundaries (entry/exit). Dozer will make sure that your data transfer objects from the database do not bleed into the presentation or into external consumers. It can also help map your domain objects to external APIs calls and vice-versa.
Enhancements:
Bug Fixes
- Incorrectly recognizing JDK 6.0 1717547
- Null pointer on MappingProcessor at Line 282 1717318
- Change the way we determine JDK Version 1715819
- Lost and Duplicated Objects 1715496
- Fix Map VO with no custom mappings 1713550
- Propagate exceptions while parsing allowed-exceptions xml 1713242
- NPE when Date String when no date format specified 1711580
- inappropriate subclass mappings applied 1674199
- Inheritance mapping not working correctly 1486105
- bidirectionnal mapping with sets subclasses 1664984
Feature Requests
- Change util classes to static 1713604
- Add PMD and Findbugs reports 1712886
- Remove NotFoundException and DozerRuntimeExceptions 1712513
- Add class level javadoc for classes missing it 1696636

Jolt is a Java Virtual Machine Daemon. This program provides a means to invoke the JDK tools javac, javadoc, and jar from the command line while reusing the same JVM instance across invocations.

Jolt daemon is intended primarily for use as a helper tool to make compilation of Java code with make as fast as (and potentially faster than) with Jakarta Ant.

It can also be used to run arbitrary Java programs (as with java); this is particularly useful for command-line utilities that are run over and over, where the cost of launching the JVM each time would be prohibitive (or at the very least, annoying).

Usage:

The `runjolt shell script can be used as a wrapper for the `jolt binary. It checks for the presence of the JAVA_HOME environment variable (which should be set to the top-level installation directory of JDK 1.4.0 or later) and augments LD_LIBRARY_PATH accordingly before invoking `jolt proper.

Drools is a Rules Engine implementation based on Charles Forgys Rete algorithm tailored for the Java language. Adapting Rete to an object-oriented interface allows for more natural expression of business rules with regards to business objects. Drools is written in Java, but able to run on Java and .Net.
Drools is designed to allow pluggeable language implementations. Currently rules can be written in Java, Python and Groovy. More importantly, Drools provides for Declarative Programming and is flexible enough to match the semantics of your problem domain with Domain Specific Languages (DSL) via XML using a Schema defined for your problem domain.
DSLs consist of XML elements and attributes that represent the problem domain.
Enhancements:
Bug
- DROOLS-294 - WorkingMemory synchronization is not complete (Barry Kaplan)
- DROOLS-314 - MethodMetadataSources need a stopping Class (Barry Kaplan)
- DROOLS-318 - WorkingMemoryEventListenerProcessor implements wrong interface (Barry Kaplan)
- DROOLS-347 - Maven build of drools-spring-jdk5 fails on Mac OS X (Andy Barnett)
- DROOLS-367 - Wrong rule executed when modifying object in workingmemory (Michael Neale)
- DROOLS-374 - Caching of classloaders in causes problems with hot deployment in some J2EE containers (Michael Neale)
- DROOLS-376 - Make source file (c) headers consistent with codehaus (Michael Neale)
- DROOLS-386 - Bug with the Escalation example? (Robert Laflamme)
- DROOLS-401 - Missing semaphore types in schema file (rules.xsd) (Edson Tirelli)
- DROOLS-403 - no-loop incorrectly removes all instances of a rule from the agenda (Michael Neale)
- DROOLS-409 - rename getNoLoop to isNoLoop to obey JavaBean naming convention (Mark Proctor)
- New Feature
- DROOLS-303 - Default rule-method parameter annotation (Barry Kaplan)
- DROOLS-360 - Maven goal for drools-all-src-XXX.zip (Mark Proctor)
- DROOLS-361 - Auto add RuleSet to RuleBase (Barry Kaplan)
- DROOLS-363 - Decision tables in spreadsheets (Michael Neale)
- DROOLS-383 - Integrate java:functions feature in decision tables. (Michael Neale)
- DROOLS-388 - Support for application data (variables), per rule duration, salience and names (Ricardo Rojas)
- DROOLS-408 - Xor Group so only one rule can fire for a specific group (Mark Proctor)
Improvement
- DROOLS-296 - Allow for default id value in parameter annotations (Barry Kaplan)
- DROOLS-297 - Allow multiple consequence annotations per rule (Barry Kaplan)
- DROOLS-301 - Remove Drools prefix from annotations (Barry Kaplan)
- DROOLS-309 - MethodMetadataSource to ignore certain classes (Barry Kaplan)
- DROOLS-310 - Condition sharing for POJO rules (Peter Royal)
- DROOLS-348 - JDK 1.3 no longer supported (Barry Kaplan)
- DROOLS-350 - Utilize 1.4 nested exceptions (Barry Kaplan)
- DROOLS-357 - Packaging between factory and meta needs some attention (Barry Kaplan)
- DROOLS-364 - Update spring libs and config files for 1.2 (Barry Kaplan)
- DROOLS-372 - Update Groovy to JSR-03 (Mark Proctor)
- DROOLS-381 - Add object-condition tests to RuleBuilderTest (Barry Kaplan)
- DROOLS-387 - add ability for a DSL to acces the XML namespace information in a Configuration (James Strachan)
- DROOLS-402 - Refactor maven.xml and drools:dist to make it faster and more intelligent (Mark Proctor)
- DROOLS-410 - Update Janino to 2.3.8 (Mark Proctor)
Test
- DROOLS-346 - Ant build.xml doesnt run drools-jsr94 unit tests (Andy Barnett)
- Task
- DROOLS-351 - Remove drools-annotation and derivitives from 2.1 (Barry Kaplan)
- DROOLS-370 - Add in drools-decisiontables subproject (Michael Neale)

Studs MVC Framework+ contains a port of Apaches Jakarta Struts to PHP, though the libraries included in the rest of the project are much more vast.
In order to implement the Struts port, it was necessary to build a core, object-oriented API in the style of the JDK and the Jakarta Commons, a servlet container to handle HTTP requests and to invoke servlet classes, and finally, a parsing engine for JSP-style template pages.
In the end, the result is an environment which is very similar to that provided by a J2EE Web Container, only everything is implemented in PHP.
While it was possible to carry over many of the concepts, designs and mechanisms from J2EE, some limitations do exist due to the nature of the PHP programming language, such as the lack of checked exceptions (runtime only).
Horizon: An Object-Oriented Environment and API
Horizon bootstraps PHP, cloaking it with a core object layer and adding missing functionality, such as imports based on qualified classname, classloading, runtime exception handling, logging, reflection, iterator language constructs and common libraries, such as an XML Digester. Once horizon takes over, the whole nature of programming in PHP changes dramatically.
Stratus: An HTTP Servlet Container
Stratus brings the servlet model to PHP. The two core features are the web.xml parsing and the doService() method call. PHP hands off what it knows about the request to the Stratus HTTP processor and it dispatches the request to a servlet mapped to the URL pattern, paralleling the workflow of Java Servlets. One crucial aspect of Stratus is that it retains state from one page request to the next by use of PHPs serialization, despite claims that PHP is incapable of this task.
Phase: PHP Server Pages Engine
The most exciting part about this project is the JSP compatible parser and compilation engine. There are a horde of templating engines for PHP, but nothing has topped JSP custom tag libraries when it comes to flexibility, ease of use and integration with the business layer. Phase is a servlet which parses regular JSP syntax, with the exception of scriptlets, which are handled by the PHP parser. Phase also ships with a handful of JSTL-like core tab libraries for data manipulation and output, supporting a full implementation of EL.
Studs proves that PHP is a very capable object-oriented language and that it is possible to use best design practices despite limitations in the language. The runtime exception handling layer should be proof that anything is possible.
The reason I really like PHP is because the core functions are so rich that under the covers, PHP can do operations very efficiently, relying on interfaces to hide the implementation details.
Enhancements:
- Automatic reload of Studs configuration file if changed [Studs]
- improved handling of DTD validation for web.xml and struts-config.xml
- get_qualified_class() migrated to Clazz::getQualifiedName() and optimized [Horizon]
- umask() behaves consistently, globally setting the file create permissions [General]
- confirmed that the ternary operator works in EL and documented it [Phase]
- throw exception if web.xml cannot be read in the include path [Stratus]
- it is possible to eliminate index.php from URL and use mod_rewrite instead [Stratus]
- modified EL processing so that arrays can be referenced as foo.bar or foo[bar] so that cases where native arrays are used in place of HashMap will still comply with JSTL EL syntax [Phase]
- changed from Hashtable to HashMap across application [General]
- changes are detected in the Studs config files (struts-config.xml) and the ActionServlet is automatically reloaded if their timestamps have been modified [Studs]
- fixed bug in Assert that caused assertFalse() to fail [Horizon]
- reimplemented the phase string taglib [Phase]
- fixed token handling in form taglib so that now they are usable [Studs]
- redirect taglib can take url as body [Phase]
- enabled more flexibility in specifying configuration directories [General]
- halt with better message when servlet work directory is not writable [Stratus]
- enabled handling of multivalued paramaters in Studs [Studs]
- added HtmlCheckboxTag and HtmlPasswordTag [Studs]
- ActionForm generator [Studs]