jvanzyl 01/07/26 14:03:51
Modified: . NOTES
Log:
- adding notes on what should be done next with torque.
Revision Changes Path
1.3 +25 -1 jakarta-turbine-torque/NOTES
Index: NOTES
===================================================================
RCS file: /home/cvs/jakarta-turbine-torque/NOTES,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- NOTES 2001/07/24 00:46:56 1.2
+++ NOTES 2001/07/26 21:03:51 1.3
@@ -7,4 +7,28 @@
in Fulcrum. The classes should be moved from Fulcrum into
this repository and Torque should be made to work on its own
and be embeddable in applications. The DBService in Fulcrum
- should be a wrapper around Torque.
+ should be a wrapper around a Torque.
+
+o Separate the connection pool and make it pluggable
+ so that torque can easily be integrated into other application
+ that already use PoolMan, or the commons connection pool, or
+ the struts connection pool or whatever
+
+o XML an configuration
+
+o Use the digester to turn the datamodel into an object and
+ get rid of the dependency on xerces. It would be nice to
+ use the digester with MinML so that the distribution can
+ be tiny
+
+o Get rid of the Log wrapper in all the code and use the log4j
+ Category c = Category.getInstance(classname) method so
+ that torque can easily be integrated into other apps. Either
+ log4j or the logging API will dominate and I'm going to take
+ log4j. But as Ceki has noted they are so similar it is very
+ easy to change from one to the other
+
+o Some analysis on what we actually have would be prudent. Torque
+ is somewhat based on the work of Scott Ambler and I would like
+ to know where it is the same and where it diverges so we know
+ what we're dealing with.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
