Shibboleth Developers

["Tom Scavo" <>]

On 2/6/07, Chad La Joie 
<>
 wrote:
> 1. Using the ErrorLog/TransactionLog elements which configures log4j in
> a programmatic manner.  This does not allow for logging information from
> third-party code (extensions) or changing things like the conversion
> pattern (the string that tells Log4J how to form it's logging messages).

Extension logging would be good, yes.

> 2. Using a Log4J configuration file which some people find to be
> confusing and difficult to configure.

Log4j config files are most confusing, I agree.

> Currently I am trying to decide how best to approach configuring logging
> in 2.0.  I am currently leaning towards dropping IdP config file based
> configuration in favor of deployers working with their container, in
> whatever manner is appropriate for that container.

How would this address the logging needs of command-line tools?  It
would be good if API calls to the Shib code base were logged, I think.
In fact, the project we're working on right now doesn't require a
container at all.

Thanks,
Tom