Bridging the gap between relational and Java objects
Studies indicate that over 90% percent of business applications use a relational database to persist their data
and a significant factor of a developer's development time is spent writing code that deals with submitting
queries to a database.
In order to achieve scalability, performance, reusability and manageability, it is very important that you
decouple the business logic from the data access logic. The J2EE blueprints
suggest using Data Access Objects
(DAO) to encapsulate any data access in order to keep your business logic clean and simple. Whether you are
developing a stand alone application, a Java servlet or your code runs within the context of an application
server, it is always good practice to have separate classes that deal with the database. In a typical enterprise
application, there can potentially be hundreds and even thousands of tables for which a developer needs to
write corresponding objects in Java; that is where DBArchitect comes in.
What's new in version 2.0
JDBC Manager to handle CLASSPATH
Insert performance logging statements in your DAO classes
Includes Synametrics Logging Framework
Many bug fixes
Works with any JDBC compliant database including Oracle, Sybase, IBM DB2, Informix, MS SQL Server and others.
Automatic relational mapping to Java objects
Java code generation for Data Access Object and its collection
Sample client to test generated code
Java code generation for Value object and its collection
Code for container managed entity bean including Home and Remote interface as well as classes for implementation and primary key.
Create code with full javadoc comments.
Support for multiple platform including Windows, Solaris, Linux, AIX, HPUX, Mac and others.
JDK/JRE 1.2 or higher
64 MB Ram (128 Recommended)