You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@turbine.apache.org by jv...@apache.org on 2001/10/30 03:38:23 UTC
cvs commit: jakarta-turbine-torque NOTES
jvanzyl 01/10/29 18:38:23
Modified: . NOTES
Log:
- log wrapper has been removed
Revision Changes Path
1.7 +3 -7 jakarta-turbine-torque/NOTES
Index: NOTES
===================================================================
RCS file: /home/cvs/jakarta-turbine-torque/NOTES,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- NOTES 2001/10/27 21:16:05 1.6
+++ NOTES 2001/10/30 02:38:23 1.7
@@ -21,13 +21,6 @@
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
@@ -45,6 +38,9 @@
[JSS] Not really database agnostic though. Must be implemented
conditionally.
+
+ [JVZ] But it has to be made to work transparently. The specifics
+ should be in the RDB specific object. The adapter probably.
o using proxies for large objects. if you had a user object
that had 50 attributes it would more efficient to create
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>