Home >> All >> com >> lutris >> dods

•	com.lutris.dods.builder.* (28)	•	com.lutris.dods.exceptions.* (3)	•	com.lutris.dods.gui.* (44)
•	com.lutris.dods.store.* (12)	•	com.lutris.dods.util.* (1)

Package Samples:

• com.lutris.dods.builder.engine
• com.lutris.dods.builder.generator.base
• com.lutris.dods.builder.generator.bdo
• com.lutris.dods.builder.generator.datainterface
• com.lutris.dods.builder.generator.dataobject
• com.lutris.dods.builder.generator.datastruct
• com.lutris.dods.builder.generator.query
• com.lutris.dods.builder.generator.sql
• com.lutris.dods.exceptions
• com.lutris.dods.gui.editors
• com.lutris.dods.gui
• com.lutris.dods.gui.importer
• com.lutris.dods.gui.table
• com.lutris.dods.gui.tree
• com.lutris.dods.store.doa
• com.lutris.dods.store.doml
• com.lutris.dods.store
• com.lutris.dods.util

Classes:

• DataObjectException: DataObjectException class, used by Business Objects, catch all the DataObject Exceptions, will be passed to POs and handled there. Need to state the reasons. Usage: import myapp.business.*; try { some access of DOs } catch (SQLException sqlEx) { if (sqlEx.getSQLState().startsWith("02") && (sqlEx.getErrorCode() == 100)) { String msg = "Update or delete DO is out of synch"; throw new DataObjectException(msg, sqlEx); } else if (sqlEx.getSQLState().equals("S1000") && (sqlEx.getErrorCode() == -268)) { String msg = "Integrity constraint violation"; throw new DataObjectException(msg, sqlEx); } else { ...
• QueryBuilder: A QueryBuilder is a helper-object used by the xxxQuery classes. Stand-alone usage: QueryBuilder qb; qb = new QueryBuilder( "cats" ); or qb = new QueryBuilder( "cats", "name, age" ); ... qb.addWhereClause( "owner.name", "Smith", QueryBuilder.NOT_NULL, QueryBuilder.EXACT_MATCH ); qb.addWhereClause( "paws", 3, QueryBuilder.GREATER_THAN ); qb.addTwoColumnWhereClause( "cat.ownerId", "owner.Id", QueryBuilder.EQUAL ); ResultSet rs = qb.executeQuery( conn ); ... qb.reset();
• DOMLFactory: This class is mostly an example use of the com.lutris.dods.project.doml package. It contains just a main method, which can be used for converting an existing DOA file into a DOML file, or a DOML file of any format into a nicely humanly-readable, indented, but possibly incorrect DOML file. This file refers to both the old style dods package dods.data and the new package com.lutris.dods.store.doa
• RDBColumnValue: After a Vector of RDBColumn objects is used to construct an instance of QueryBuilder, the QueryBuilder.getNextRow() method is used to return an RDBRow object which contains RDBColumnValue objects representing the column values in the returned row. An instance of RDBColumnValue is returned by the RDBRow.get() method. The value contained in the RDBColumnValue object is extracted using RDBColumnValue.get methods.
• ColumnNullException: ColumnNullException is thrown by RDBColumnValue.get methods when an unexpected NULL value in a column retrieved from the database. Application developers should treat ColumnNullException like other ChainedException objects. ColumnNullExceptions can be used to perform assertions upon queried data. Otherwise, they usually indicate programming errors caused by a misunderstanding of the database schema.
• DOgraphNode: This class is used by the Builder to generate two lists: 1) a list of generated .sql files in a valid execution order. 2) a list of "drop table" SQL commands in a valid execution order. The 2nd list is in the reverse order of the 1st list. The order is determined by the inter-tables references (foreign keys). The tables with no references are created first and dropped last.
• DOMLWriter: This class is a standby tool used to print DODS XML DODML files to some output stream. It is mostly a direct lifting of the Xerces sample code dom/DOMWriter.java, with some minor modifications. This file should be junked and re-written as soon as possible. As soon as that happens, the following Apache text need not apply to it...
• ColumnTypeException: ColumnTypeException is thrown by RDBColumnValue.get methods when a column value is of an unexpected type. Application developers should treat ColumnTypeException like other ChainedException objects. ColumnTypeExceptions usually indicate programming errors caused by a misunderstanding of the database schema.
• Builder: For each DataObject in the current DODSProject, the run() method invokes the source code generators described in the dods.conf file. After generating the tree of source code for for the DataObjects, a makefile is created in each directory in the tree. Finally, 'make' is run at the top directory.
• InvalidRowColumnException: InvalidRowColumnException is thrown by the RDBRow.get methods when a requested column does not exist in the current row. Application developers should treat InvalidRowColumnException like other ChainedException objects. InvalidRowColumnExceptions indicate programming errors.
• QueryException: QueryException is thrown by QueryBuilder.getNextRow and getRows methods when the database query could not be performed. Application developers should treat QueryException like other ChainedException objects. QueryExceptions indicate run-time errors in accessing the database.
• RDBRow: An instance of RDBRow is returned by the QueryBuilder.getNextRow() method. An RDBRow contains RDBColumnValue objects corresponding to the RDBColumn objects used to construct the instance of QueryBuilder. in a particular table in the database.
• DODSProject: A DODSProject is a DOPackage which is the root of a project. It contains the information about what file it is stored in and what kind of database these DataObjects will be contained in. (ie. Oracle, Informix, etc.)
• RDBTable: An instance of RDBTable describes a particular table in the database. It is used to construct RDBColumn objects which can then be used to perform database queries using the QueryBuilder class.
• RDBColumn: An instance of RDBColumn describes a particular column in a particular table in the database. It is used to construct database queries using the QueryBuilder class.
• DatabaseAdapter: This is a temporary database adapter, until I have time to figure out the Enhydra DatabaseManager classes... Yeah, kinda messy right now :)
• DOTableColumnRenderer: This class is set up to display Columns in a JTable with an Icon instead of Text. It should be extended rather than used itself.
• DataObjectApplication: This class is the heart of the Data Object Design Studio. This frame contains all of the panels and menus that make up DODS.
• TableHeaderListener: This is a standard Mouse Listener for the TableHeader. When a Column Header is clicked, the table is sorted by that Column.
• DataObjectEditor: This class is a pop-up window which lets you edit all of a DataObject's attributes (not Attributes) in a convenient window.
• DOTableComboEditor: This class is the editor which shows a dropdown list of choices for that cell. It is currently only used for one column.
• AttributeTreeSelectionListener: When a node is selected in the Attribute Editor, that node's name is displayed in the appropriate TextField.
• TableMouseListener: This class tells the table which row is selected, and it handles editing the boolean values in the table.
• GraphicalBranch: This represents one node of the Graphical Tree in the GraphicalPanel and the connections to other nodes.
• PackageEditor: This class creates a pop-up window which allows you to edit a package by changing its name and location.

Home | Contact Us | Privacy Policy | Terms of Service