MDi JLib

MicroDeveloper, Inc.TM MDi JLib 1.7.4 API Specification

The MicroDeveloper Java Library was designed to allow quick and easy access to various common tasks as they relate to database driven applications.


Other Packages
com.microdeveloper Informational classes or classes which perform no particular utilitarian need.
com.microdeveloper.common A collection of utility classes for text, date, numeric, and graphic manipulation. A collection of utility classes for date and time manipulation. A collection of APIs that are specific to database data manipulation or generic data manipulation.
com.microdeveloper.db A collection of generic database connection classes for secure, parameter driven connections.
com.microdeveloper.db.jndi A collection of JNDI based database connection pool classes for secure, parameter driven connections to Oracle databases.
com.microdeveloper.db.rectifier Provides database comparison and reconciliation functions Classes for easily encrypting and decrypting text using various DES encryption methods. Contains servlets that provide input output capabilities.
com.microdeveloper.servlets.jndi Utility servlets for debugging JNDI resources.
com.microdeveloper.util.exception Provides exception handling utility calls for extended exception manipulation Contains API's for providing basic input-output and encoding capabilities. Provides extensive logging capabilities to applications. Contains classes for manipulating property files. Provides APIs for implementing simple to complex E-mail capabilities or applications.


The MicroDeveloper Java Library was designed to allow quick and easy access to various common tasks as they relate to database driven applications.

Many of the classes follow traditional SQL or PL/SQL syntax paradigms specifically for database developers who are already familiar with PL/SQL and SQL. Other utilitarian classes provide API's that enable greatly simplified tasks such as sending a Multipart E-mail without having to understand the complexities of the underpinning architecture. This helps to consolidate common code, such as subString or Date manipulation into a common set of packages and saves a considerable amount of development time.

The database classes were originally designed for quickly accessing Oracle databases and were later extended to support other non-Oracle data sources. The underpinnings of many of the classes are distinctly Oracle flavored as a result and follow the Oracle paradigm for describing database connections. For example, the use of a properties file is very similar to the tnsnames file that Oracle uses for their OCI connections.

The creation of these database friendly classes are intended primarily for use in servlets and JSP pages where simple constructs are preferred to the often complex implementations. Some classes, such as SQLData, allow for quick, consistent data access with little more than a single command. The SQL can be stored in a simple include file or read in from a simple file. This allows the SQL to be written independently and plugged in with little or no change to the supporting code unlike JSTL and other implementations which are often more difficult to implement. It also keeps the SQL and the logic out of the JSP pages or servlets while still allowing for complex database interactions.

The database connectors themselves provide a wealth of capabilities not typically found in the vendor driver classes. This allows JSP pages to be encoded with generic application access names rather than database user names and passwords. In doing so, the username and passwords can be changed at any time without impacting any deployed pages. Only the central application map need change and the pages immediately inherit the change.

Finally, paramount to the design was the goal of establishing secure database communications without exposing the database accounts in the filesystem. Many implementations place the username and password in clear text files on the server. Unfortunately, if the server is compromised, so are the passwords and complete database information. These classes never expose the password for a database account and never store the clear text password. All of these classes encrypted passwords using strong 156-bit Triple-DES encoding. The internal mechanics of the mechanism allows each password to be unique for the connection making it more difficult to defeat. This model follows the same model as an Oracle database security mechanism.

Original classes and documentation by MicroDeveloper, Inc. 2001-2007.
Please contact MicroDeveloper Support to report bugs or problems.

By using this library you agree to the terms and conditions of the End User License Agreement.

Copyright©2001-2007, MicroDeveloper, Inc.
All Rights Reserved.

Overview documentation version 1.0.0

MDi JLib

Copyright©2001-2007 MicroDeveloper, Inc. All Rights Reserved.