[snip] > No - I've actually maked up the message and planning on posting a > detailed reply. The short answer is the the current loggging > subsystem > can be viewed as a minimal bootstrapping implementation - and > the long > answer (comming later) details a number of things that have a > signficant > impact merlin, repository, and excalibur-logger - if this is to be > addressed properly. Look out for a message titled "logging strategy". >
I'll be on the lookout for your email and thanks. Seems like creating our own logging service might be the easiest thing to do. I've never created a service for Merlin that uses/requires another of my own services but that should not be to hard. I'm almost tempted to dig into the Merlin code base and just get proper logging working but I don't know what kind of time commitment that would require. Thoughts? [snip] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
