[Wrapper-user] Feature request- use commons-logging

[Jennifer K. <jk...@si...>]

My request is to either use commons-logging throughout your app-- since 
you have essentially created your own implementation of it--
and allow through the inner spawned applications commons-logging 
messages at their relative levels (rather than only wrapping them all 
in info)..

or leave your implementation as is, but still allow through the spawned 
applications commons-logging messages at their levels rather than 
putting everything in info.

Where this is a real problem for me is the event logging. I can't send 
any of my application errors to the event log - using your code as is- 
unless I enable info .. which is way more verbose than I want to send 
to the log..

not sure if you have thought about doing this already or not, I know 
you recently reworked how you pass through stdout..
If you have thought about it-- what implementation plan did you have 
that I could perhaps follow early?

I know you capture all std out from the calling app-- so maybe you 
would have to filter each message looking for commons logging
levels and map those to the appropriate level in your app.. if you 
didn't think it reasonable to just use commons-logging wholesale. Just 
one thought...

thanks
Jennifer