Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » DTP » Suggestion of improvement of catalog loader/sql model extension code for DTP 1.5 M6
Suggestion of improvement of catalog loader/sql model extension code for DTP 1.5 M6 [message #584827] Fri, 16 March 2007 17:45
Brian Fitzpatrick is currently offline Brian FitzpatrickFriend
Messages: 500
Registered: July 2009
Senior Member
Hi all!

For DTP 1.5 M6, I have a suggestion of how to make the catalog loader/sql
model extension code easier to use for adopters. I'm interested in getting
feedback from the community at large before delivering this into the

I've tested this design in the HSQLDB case (to customize a level - Schema in
that case - to use a pipelined tree content provider and navigator content
extension to remove an IVirtualNode - Stored Procedures) and I've tested it
for Derby, which also works to customize the table loader for Schema nodes
and it works great. It greatly simplifies things by allowing much more reuse
and less re-implementing the wheel to get things done.

But I'd like to know what you think. I'll also be posting this to the
dtp-dev mailing list.

Thanks for your time!



New extension point:

Each overridden loader element provides four bits of information: product
(vendor), version, overriding class (extends one of the JDBCBaseLoader
classes), eclass (class name to indicate which model element we are
overriding the loader for)



point="org.eclipse.datatools.connectivity.sqm.core.overrideLoader ">


provider=" org.eclipse.datatools.enablement.hsqldb.catalog.HSQLDBSchema Loader "





We would introduce a new manager class to handle these overridden catalog
loaders: CatalogLoaderOverrideManager. This class provides three methods:

getDbDefinitions() returns Iterator of the DbDefinitions with registered
overriding catalog loaders

getEClasses(DatabaseDefinition) returns Iterator of the eclass names with
loaders registered for a given database definition

getLoaderForDatabase ( DatabaseDefinition, eclass name) returns an instance
of a class that extends JDBCBaseLoader that can then be cast to a particular
type of catalog loader such as JDBCSchemaLoader, JDBCCatalogLoader, etc by
the given object

Then each wrapper class in
org.eclipse.datatools.connectivity.sqm.core.rte.jdbc (JDBCDatabase,
JDBCCatalog, etc.) has code similar to this in its createLoader() method

protected JDBCCatalogLoader createLoader() {

DatabaseDefinition databaseDefinition =


JDBCBaseLoader loader =

CatalogLoaderOverrideManager.getInstance().getLoaderForDatab ase(databaseDefinition,
SQLSchemaPackage. eINSTANCE.getCatalog().getInstanceClassName());

if (loader != null) {

JDBCCatalogLoader catLoader = (JDBCCatalogLoader) loader;


return catLoader;


return new JDBCCatalogLoader(this);


If an overriding catalog loader has been registered for a particular db
definition/eclass pair, it will be returned here and passed along. If not,
we'll stick with the basic method of creating a default catalog loader.

One change was made to JDBCBaseLoader in order to facilitate being created
as an executable extension from the plugin extension registry. It had to
implement a zero-argument constructor and add a
setCatalogObject(ICatalogObject) method.

But this allows anyone implementing custom catalog loaders to use the
defaults as much as possible and only start overriding things when they need

For example, in the HSQLDB case, we just want to extend the UI wrappers for
the model enough to make the Schema object unique for HSQLDB databases. This
allows us to then intercept and remove the stored procedure collection node
from the UI.

Or in the Derby case, we just want to override the table loader to include

Brian Fitzpatrick

Senior Software Engineer/DTP Committer

Sybase, Inc.
Previous Topic:Suggestion of improvement of catalog loader/sql model extension code for DTP 1.5 M6
Next Topic:dtp 1.0.1
Goto Forum:

Current Time: Tue Apr 24 18:30:39 GMT 2018

Powered by FUDForum. Page generated in 0.01975 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software