On Fri, Jan 28, 2011 at 10:55 AM, Simon Nash <n...@apache.org> wrote: > Simon Laws wrote: >> >> On Thu, Jan 27, 2011 at 10:03 PM, ant elder <ant.el...@gmail.com> wrote: >>> >>> On Thu, Jan 27, 2011 at 2:14 PM, Simon Laws <simonsl...@googlemail.com> >>> wrote: >>>> >>>> I'd like to reduce the amount of log output we get by default by, for >>>> example, changing the endpoint registration to be fine rather than >>>> info. Anyone have any concerns about me doing that? >>>> >>> A couple of months ago i changed the default logging used by the shell >>> in the binary distribution [1] to suppress all the info messages as >>> there's so much irrelevant noise but now its really hard to tell whats >>> going on - you start a composite and nothing happens, no messages >>> about nodes, or contributions or composites or components or endpoints >>> or anything, so recently i've been thinking about reverting that >>> change. What info messages do you think you would still leave coming >>> out by default? I know you can change the logging properties level to >>> something finer but then you get literally hundreds of messages which >>> isn't very helpful either. >>> >>> ...ant >>> >>> [1] >>> http://svn.apache.org/viewvc/tuscany/sca-java-2.x/trunk/distribution/all/src/main/release/launcher/logging.properties?r1=1037517&r2=1039849 >>> >> >> What I had been thinking was that we reduce (inrcease?) the level log >> logging messages so that they don't come out by default. We then have >> at least two options for providing useful output to users; >> >> 1/ users can, either selectively or generally, specify logging levels >> to get output. We could document certain combinations that produce >> suitable output. >> >> 2/ provide pre-canned reports for use by embedders (like the shell or >> anybody else) that tell you what composites/components have been >> started what endpoints are registered etc. There are any number of >> such reports you can imagine. From an endpoint of view it could even >> be done incrementally, and if really required, remotely. We should >> have more info in the domain registry (i.e. the endpoint registry is >> just one part of it) so my last comment should ultimately be applied >> to any domain information. >> >> We have a very few examples of 2 already that could be re-purposed. For >> example >> >> - dumping built composites. See code at bottom of >> >> http://svn.apache.org/repos/asf/tuscany/sca-java-2.x/trunk/modules/builder/src/main/java/org/apache/tuscany/sca/builder/impl/ModelBuilderImpl.java >> >> - dumping out WSDL interfaces. See code from 1.x >> >> http://svn.apache.org/repos/asf/tuscany/sca-java-1.x/trunk/tools/contrib2wsdl/src/main/java/org/apache/tuscany/tools/contrib2wsdl/Contrib2WSDL.java >> >> Simon >> > I find the log messages useful, but I'm not the typical user :-) >
If having info log messages isn't desirable in some circumstances how about adding a "quiet mode" to the runtime and have everywhere that does info logging use fine logging instead when quiet mode is set. ...ant
