[JBoss-dev] org.jboss.ejb.plugins.cmp.jdbc.WrappedStatement

[Scott M S. <sco...@jb...>]

Cleanup of the connector jboss-common-jdbc-wrapper.jar dependencies on
the jboss.jar through the
org.jboss.ejb.plugins.cmp.jdbc.WrappedStatement interface requires
moving the org.jboss.ejb.plugins.cmp.jdbc.WrappedStatement to the
connector module along with the only users of this interface,
org.jboss.ejb.plugins.cmp.jdbc.keygen.JDBCInformixCreateCommand and
org.jboss.ejb.plugins.cmp.jdbc.keygen.JDBCMySQLCreateCommand. The
WrappedStatement would have to be put into the
jboss-common-jdbc-wrapper.jar as its implemented by
org.jboss.resource.adapter.jdbc.WrappedStatement, and a new
jboss-jdbc-keygen.jar created with these driver specific generators to
form a dependency graph like:

jboss-common-jdbc-wrapper.jar jboss.jar
       |                         |
       ___________________________
                     |
            jboss-jdbc-keygen.jar

Just moving the org.jboss.ejb.plugins.cmp.jdbc.WrappedStatement
interface to the connector module creates a circular dependency between
the connector and server modules. The connector module already depends
on server.

It might make more sense to move all of the
org.jboss.ejb.plugins.cmp.jdbc.keygen classes to the connector module to
avoid splitting classes in the same package across jars.


http://jira.jboss.com/jira/browse/JBAS-2250
=20
xxxxxxxxxxxxxxxxxxxxxxxx
Scott Stark
Chief Technology Officer
JBoss Inc.
xxxxxxxxxxxxxxxxxxxxxxxx=20
=20