i share the blame for propagating this mail log stuff (see my earlier forum post and
cvs commits), sorry.
but would still be nice to treat conversational logging specially and be able to
manage logging via jmx, as opposed to manually going in and redeploying log4j.xml.
only way to treat
That is an AWESOME idea.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3829627#3829627
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3829627
---
This SF.Net email is
thanks --- looks like someone halfway beat me to it though --- i'm looking in
3.2.4RC2, and there's an mbean called
jboss.system:service=Logging,type=Log4jService. folks can take a peek to see what it
offers.
doesn't seem as fine-grained as what we're talking about, and rather seems to rely on
Lets put this off though. We need to focus on getting M1 out and planning for what
goes in M2. I posted some ideas on the wiki (refined the planning). It is ambitious
but we can revise it as needed.
View the original post :
absolutely. its in my to-do list at low priority, so it won't get touched till all our
M1 stuff gets done.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3829663#3829663
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3829663
add it as a detail somewhere on the plan on the wiki. It should go *under* some
bullet on a sub page or something. (still working out what the format of that page
should be but the first page should definitely be high level)
View the original post :
the log4j sniplet I posted didn't come through all the way. I'll repost it on the
wiki when I write the docs for mail services M1. This week I'm mostly testing, fixing
bugs and writing docs (aka the dirty work). I'm counting on you guys to nail the few
final issues.
View the original post :
