Hi, I have talked with Dirk Kraemer and Bradley Handy about how to package the "connectionFactory" dbforms' contribution. Bradley has already integrated this stuff with his "multiple connections" feature.
This contrib will add a plugin system for jdbc connection pool libraries. Up to now, this factory supports the following connection pool packages: - jakarta commons dbcp (initial code done by Eric Pug) - protomatter (http://protomatter.sourceforge.net/) - single connection (no pool at all) support for other systems is done coding simple "provider" classes and set the right configuration into the dbforms xml config file. This is the problem: the connectionFactory classes derive from a not-yet released powtoolkit package See [http://sourceforge.net/projects/pow2toolkit] and [http://www.pow2.com/download/pow2toolkit_20020926.zip (*)] for the latest unofficial release. So, to integrate the classes from the pow2 package there are 2 possibilities: 1) keep that classes into the pow2toolkit package (com.pow2.dao.*) and add a "pow2 connectionFactory" jar (about 6 classes) into the dbforms' classpath 2) move that classes into the dbforms' package Here's a snapshot from a previous discussion between Dirk and me >> if we want to integrate it, we should put it into a dbforms package, >> maybe org.dbforms.util, where also DbConnection is. You are the author, so >> you may decide in the end. Maybe org.dbforms.pool and >> org.dbforms.pool.adapters? > For me it's OK. Time ago I spoke with Bradley and he suggest me to keep the > connectionFactory stuff into a "pow2" package; my idea instead was to put the > c.factory sources into the dbforms sources tree. > I think the latter is a better solution in terms of "project integration"; > Bradley tells that keeping the two packages separated is a better idea in > terms of "code manteinance" (it's fine, too). > > I think that moving the c.factory code into the dbforms package will provide > better opportunities to other contributors to extend or tweak that stuff. Both the solutions are good. So I'd like to know what's your idea about the integration of "common" packages (example: dbforms and pow2toolkit or dbforms and yourOwnStuff library) Thank you, Luca ------------------------------------------------- (*) How to compile the pow2connectionFactory jar: unzip the archive, go to the root directory and digit: > ant all or use the "ant-buildAll.bat" icon (win32) Then go to the "build" directory and pick the generated "pow2ConnectionFactory.jar" file. (use "ant javadoc" to build the javadoc documentation (with my poor english around ;^) dependencies: - log4j (same version used by dbforms) - protomatter [http://protomatter.sourceforge.net/] to compile the ProtomatterConnectionProvider class ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ DbForms Mailing List http://www.wap-force.net/dbforms
