Hey Dan,
We were discussing changing the dependency of the SalesForce and WSDL to Relational
importers from com.metamatrix.modeler.dqp.config.ConfigurationManager to the
JDBCImportPostProcessor. When I looked into that class last night I found that it's
not going to work for me without substantial change because its very JDBC specific. My
importers don't set the same binding properties as the JDBC importer, and don't
have to edit classpaths and such. It seems to me that the ConfigurationManager is really
the right abstraction for what I need. It allows me to find the right connector type and
set any values I want on it. Each of my importers has different values to set in the
bindings. Is there some reason that we can't leave ConfigurationManager as the public
API (assuming that it might change in this release because of the JCA changes)?
~john