@Log looks hot. I want it. But I'm not writing a web app. I don't know
anything about Tapestry and don't really want to!
Here are my initial questions!
1) Is it even possible to use @Log outside of a webapp?
If the answer to 1) is No, then the rest of my questions are quite possibly
moot.
2) What is the minimal set of software/jars I would need to download to make
use of this annotation?
3) I'd rather not ship my software with jar files supporting web applcations
just to get @Log! What would it take to extract @Log from the rest of the
Tapestry source?
4) Though I've spent less than an hour browsing tapestry.apache.org, I have not
yet stumbled on a "system requirements" page. I'm assuming you only need
JDK1.5 and not 1.6?
5) @Log is part of Tapestry. Would it make more sense to move it to some more
fundamental logging project like SLF4J making it more accessible to a larger
audience?
6) Why does @Log log trace information at DEBUG level instead of TRACE level?
I see that SLF4J does indeed include a trace() method.
7) I've spent the last several hours researching annotations with the aims of
figuring out how to write such an annotation myself. The examples I've read
through so far on APT are limited to generating informational messages at
compile time. Though I know it's capable of much more (including source code
generation) I wasn't sure @Log was even possible until I stumbled on it here.
I'd like to understand how you did it! I've checked out the Tapestry source
code and started poking around. Can you suggest what classes I should look
at? Or perhaps suggest a book or good tutorials that would teach me enough to
do what you've done with @Log?
Much thanks,
Matt Busche
Lakewood, CO
