Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Date: Thu, 9 Dec 2004 23:49:53 +0100
Message-Id: <200412092249.iB9MnruB027435@ajax.apache.org>
From: bugzilla@apache.org
To: commons-dev@jakarta.apache.org
Subject: DO NOT REPLY [Bug 32618]  -
    Enterprise Commons Logging : Globalization & more

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=32618>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=32618


------- Additional Comments From rsitze@apache.org  2004-12-09 23:49 -------
    B.1.  Functional alignment with JSR-47 concepts.
          JSR-47 has 3 trace levels:  FINE, FINER, FINEST
          JCL has 2 trace levels defined today: debug,
          trace which corresponds to JSR-47 FINE and
          FINEST in the current implementation.

          The JSR-47 FINER level has no corresponding APIs
          in JCL.  The expectation is that the FINER level
          be used for "class/method level flow".

          We propose a set of API's that would correspond
          to the JSR-47 FINER LEVEL, but more generally
          support the "class/method level flow" logging.

          - enter(Class clazz, String methodName,
                  Object message);

          - enter(Class clazz, String methodName,
                  Object methodArg,
                  Object message)

          - enter(Class clazz, String methodName,
                  Object[] methodArgs,
                  Object message);

          - exit(Class clazz, String methodName,
                 Object result,
                 Object message);

          - exit(Class clazz, String methodName,
                 Throwable exception,
                 Object message);

          These being "new" API's, it is reasonable to have
          'Log' level behavior... updating Log or only
          supporting in EnterpriseLog might be an interesting
          discussion point.

          The JCL debug level is described (in the user's
          guide) as appropriate for "detailed information
          on the flow through the system."  As a best
          practice, would like to suggest that this be
          for "component level flow", i.e. crossing
          component boundries.  This being a guideline,
          we see no conflict with current usage.
          This is in-line with current JSR-47 expectations.
          This does raise a question: would a set of
          API's to support this notion be appropriate?
          Something along the order of:

          - enterComponent(String componentName,
                           Class clazz,
                           String methodName,
                           ...);

          - etc.


-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org