recognizing that big xml strings are a horrible way to configure applications, some folks have resorted to annotations/attributes. the problem with this approach is that annotations generally end up being just as big a kludge and really only cast the xml across multiple files, which isn't always bad. what i'd like to see from open source teams is an initial preference for code-driven configuration (see pico + nanowar). i am extra baffled because code-first would seem the logical path to me from a test-driven perspective. toplink got it right with mappings.
besides, if Matthew says "put it in pico," you best put it in pico. ack.