[LOGGING-89] [logging] Enterprise Commons Logging : Globalization & more

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Won't Fix

Environment

Operating System: All
Platform: All

• Bugzilla Id: 32618
• Assignee: Unassigned
• Reporter: Richard A. Sitze
• Created: 10/Dec/04 07:44
• Updated: 09/Jul/14 20:14
• Resolved: 15/Jul/13 21:07

Description

IBM would like to open a discussion within the Jakarta commons community
on evolving the Jakarta Commons Logging (JCL) API's to support Enterprise
level logging functionality. We recognize the value that a "logging
implementation independent API" brings to open source component
development, and would like to work with the community to accomplish this
goal.

We present a set of requirements as a baseline for the discussion, a
proposal for meeting these requirements, a number of points of discussion,
and attached are two Java source files that correspond to the discussion
below.

Requirements:

We recognize that the community has an overriding
requirement:

A.1. Evolution: maintain compatibility with the
current LogFactory/Log interfaces.

We have ONE primary requirement:

A.2. Globalization

Having opened the door, we'd also like to propose a few
other requirements:

B.1. Functional alignment with JSR-47 concepts.

B.2. Fix fragile configuration problems - Currently
the user has NO idea which impl is in effect.
All the default/fall back behavior means that in
the end we have an apparent non-deterministic
logging implementation. Errors in config file
names, classpath errors, classpath ordering,
etc., can all change the behavior... with no
idea which is in effect.

The fundamental problem with the current factory
is that it is dependent on "passively"
identifying a logging implementation.

We propose one solution below, but would ask a
more general question: any new bright ideas?

Issue Links

• is duplicated by: LOGGING-121 Extend the org.apache.commons.logging.Log interface for suitable use