|
Featured Reviews
|
 SqlSpec |
|
Includes a comment editor supporting SQL Server, Oracle, and more.
|
|
| Universal SQL Editor |
|
Support Oracle, DB2, SQL Server, Sybase and other ODBC databases.
|
|
| Softerra LDAP Browser |
|
A premier explorer like LDAP client designed for Windows and admins.
|
|
| Secure Auditor |
|
IT security assessment software which performs database auditing.
|
|
| DBA Easy Control |
|
A unique versatile database management suite for Oracle DBA.
|
|
| Secure Bytes |
|
Solution for conducting automated audits on Windows, Oracle and SQL.
|
|
|
J-Database Exchange (JDX), provides a very efficient solution to a very common need for application programmers - transactional persistence(storage) of Java business objects in relational databases.
Applications come and go, but the information about business objects needs to be recorded on a permanent storage medium so that it is available the next time a continuing or concurrent or a newly started application needs it. Examples of business objects are: quotation, purchase order, customer info, invoice, product info, pricing info, sales transaction, patient record etc.
JDX provides a very natural object-oriented interface for storing and retrieving Java objects using relational databases. In most cases, JDX will save about 30-70% of the development cost for typical new Java applications by automating the tedious, time-consuming and error-prone task of object-relational mapping (OR-Mapping). Application developers can focus their efforts on business logic, rather than being overwhelmed by writing and maintaining tedious SQL code for object persistence.
JDX provides support for complex object-modeling including class hierarchies. JDX allows integration with legacy data to leverage existing investment. To meet mission-critical performance needs, JDX employs an extremely scaleable architecture.
JDX does not modify your application source files - all object relational mapping happens in a separate layer. Consequently your application becomes data independent because the same application can work against different backend databases without any modifications! In fact, the object-relational mapping specification may be shared between independent applications. This provides a welcome relief from the proliferation of the complex object-relational mapping code. |
|
|
|
|