Watch, Follow, &
Connect with Us

For forums, blogs and more please visit our
Developer Tools Community.


ID: 20331, Adligo Open Source Components

by Scott Morgan Email: scott@adligo.com


Java Swing Components based on the JBuilder Libraries.
Server side components used for passing data sets to a swing client.
Download Details
FTP  download also available 0 bytes
CDN Login Required to Download. (You will be redirected to the login page if you click on the Download Link)
To download this, you must have registered:
A free membership

For JBuilder, Version 1.0  to 1.1 5 downloads
Copyright: Open Source or other


Size: 0 bytes
Updated on Thu, 17 Jul 2003 13:27:33 GMT
Originally uploaded on Thu, 17 Jul 2003 13:26:05 GMT
Description
The Adligo Open Source Components are divided into four parts. First in the Adligo Open Source Components is the XMLT or XML Template parser. This component allows developers to store all of the potential query language (SQL or EJB QL) in XML Templates. This gives the following advantages; 1. All of the query information necessary for querying a particular Entity Object is normalized into one location. This eliminates potential errors caused from small discrepancies. For instance if a developer embedded a SQL statement in the code; SELECT Fname, Lname FROM persons WHERE Fname = 'george' And then had a second statement some where else in the code; SELECT Fname, Lnames FROM persons WHERE Fname = 'frank' The code would burp a error due to the discrepancy Lname vs Lnames. If this query information was stored in a XML Template as the following; SELECT Fname, Lname FROM persons WHERE Fname = 2. The code used to send the query knows nothing about the way that the data is stored. This is one of the major hurdles that the EJB spec tackles. However the difference between the EJB model and the XMLT model is that the EJB model makes a Application Server mandatory. In Applications where there are less than 100 clients using a particular Data Base and the data base is large the traditional client server model is quite possibly superior than a N-Tier model because of the simplicity of the model. The XMLT model allows developers to switch between a two tier model and a N-Tier model with a very small amount of code (less than fifteen lines). 3. Storing your query language in the XML Template format will allow you to auto generate all of your search panels by using the Adligo Treefinder. http://adligo.com/treefinder/index.html Please see the following link for directions on how to format your XML Templates. http://adligo.com/treefinder/instructions.html Second in the Adligo Open Source Components is the Server Library. The Server Library currently is simply a EJB Session Bean that provides Data Set Data from a SQL Data Base (tested Oracle, SQL Server, PostgressSQL). It can be used on the Client for a 2 tier model or in a application server for a N-Tier model. In the future this will also allow Data Sets to be provided from EJB Entity Beans. This bean currently uses a tid (table id), version combination where tid is a unique persistent identifier for each row or entity. This is used in the Adligo code to keep more than one user from editing a particular row "at the same time". Third in the Adligo Open Source Components is the Entity Library. This Library includes the Fat Client Provider and Resolver which have been used to provide and resolve data from the Adligo Server Bean. Also, this Library contains a number of Data Set Entity Objects for simple things like orgs (organizations), persons, addresses, electronic addresses exc... Forth in the Adligo Open Source Components is the Swing Library. This provides panels to show most of the Entity objects. For instance there is a panel for Addresses. Also there are a bunch of other swing components mostly dealing with dialog boxes.

For more information, see http://www.adligo.com/software.html

   Latest Comments  View All Add New

Move mouse over comment to see the full text

Could not retrieve comments. Please try again later.

Server Response from: ETNACDC04