Re: XML Calabash and logging

Sounds good!

> with commons-logging-1.1.1 thrown in for good
> measure because the Apache HTTP libraries seem to require it

IIRC you can also replace common-logging-1.1.1 by a “facade” library (called jcl-over-slf4j) that delegates commons-logging API calls to slf4j, see:

  http://www.slf4j.org/legacy.html

Romain.


On 3 sept. 2014, at 02:51, Norman Walsh <ndw@nwalsh.com> wrote:

> Hello world,
> 
> I find the subject of logging in Java to be extraordinarly
> complicated. I've been trying to work through some weirdness in the
> logging behavior of XML Calabash.
> 
> Complicated or not, there are clearly some benefits to "doing it
> right." In particular, I've removed all those .printStackTrace() calls
> and things are moving towards having reasonable info/debug/trace level
> messages.
> 
> FWIW, I've settled, perhaps mostly by accident, on using SLF4J as a
> front end on LOG4J2 with commons-logging-1.1.1 thrown in for good
> measure because the Apache HTTP libraries seem to require it.
> 
> I've poked at the XML Resolver library code to use those loggers as
> well.
> 
> If you're curious to see the effects, there's a log-hacking branch
> checked into github now (it's going to be transitory, but it'll be
> there at least until I can figure out why Travis CI can't get a
> passing build with it).
> 
> Comments and suggestions most welcome.
> 
>                                        Be seeing you,
>                                          norm
> 
> -- 
> Norman Walsh
> Lead Engineer
> MarkLogic Corporation
> Phone: +1 512 761 6676
> www.marklogic.com