This one time, at band camp, Marc Guillemot said:
MG>I think that Castor doesn't use log messages enough intensively as it should
MG>to inform about it's work.
MG>For instance I just have to go with the debugger to find why an object
MG>wasn't loaded. With this way I've found the cause of the problem and could
MG>fix it, but it could havebeen really easier for instance if Castor logs some
MG>information on discarded exceptions (in my case ObjectNotFoundException in
MG>org.exolab.castor.jdo.engine.OQLQueryImpl).
MG>
MG>Second question: why doesn't Castor use the great log4j or common logging
MG>from Apache instead of it's own poor featured log classes?
Marc,
I'm actually working on this right now. I was planning on implementing
the Jakarta Commons Logging package using Log4J as the default logging
mechanism. But as I'm working with the Commons Logging I'm not sure
that I care for it. I'm thinking of just implementing straight Log4J.
Bruce
--
perl -e 'print unpack("u30","<0G)[EMAIL PROTECTED]&5R\"F9E<G)E=\$\!F<FEI+F-O;0\`\`");'
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
