jUDO is short for "java Universal Data Objects" and
speeds up development/maintainence and remove database-vendor dependency
for applications using databases. You should use jUDO whenever you don't
want to use EJB's. It will also work for .NET in a near future.
You don't write ANY database-code ,you only have to
specify the container classes and the Interfaces for the Models and
then jUDO creates the implementation for you runtime, no source is generated!!!
It derives all info need to by your Interfaces method names ,that follows
name-pattern rules. In case you need some special access method you either
add a plugin for this or simply go directly against the database.

jUDO is not as "configurable" and advanced as other much more professional software like Castor , Hibernate etc, BUT since jUDO derives the database from your code, there is NEVER EVER mismatch between code/database.

Below is an example with one Table User and main class that test some
of the accessor methods. NOTE!! this is all source code needed since the
implementation itself are manufactured troughout your given method name.
NOTE: No code is written for accessing the database ,isn't this great ???

public Country fkGetFkcountryById(Integer id) throws Exception; // get Country object pointed by fkcountry public Country fkGetFkcountryByIdName(Integer id) throws Exception; // get Country object pointed by fkcountry

public Class container=User.class; // The variable "container" binds this model to its conteiner. }

NOTE1: jUDO matches every
method name and manufactures "code" for you ,this is done at startup.

NOTE: the classes above are ALL that is need for 1 table , NO CODE !!!!!!
only fields and methods names .

Below is a test program ,that actually does a lot , e.g executes
the methods that we only have specified the names in the INTERFACE.
(jUDO has manufactured the implementation , out of the method
names)