Hi Jim/Jeremey
I understand the intent, but this doc doesn't really tell me how I
configure this.
I don't want to define my own log API I just want to use one. Do you
have an example of this kind of usage?
@Monitor
setMonitor(java.util.logging.Logger mylogger)
?
If so how do I configure this with log4j for instance? I just want
something that works and doesn't require me to implement a logging
framework on the back end.
Thanks
andy
At 15:35 07/09/2006, Jim Marino wrote:
On Sep 7, 2006, at 6:07 AM, Jeremy Boynes wrote:
Can you point me at the recommended way of logging? I could not
immediately find any code that did this.
We need to write logging guidelines I guess. There have been
various emails about this, look for MonitorFactory. The basic idea
is that to log a component:
* defines a monitoring interface that it will call to emit events
* marks that as a dependency with a @Monitor annotation
* an implementation of that interface is injected by the runtime
* the component makes the calls as needed
Here's a writeup: http://incubator.apache.org/tuscany/monitoring.htm
We've basically externalized logging/monitoring in the runtime.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
_______________________________________________________________________
Notice: This email message, together with any attachments, may contain
information of BEA Systems, Inc., its subsidiaries and affiliated
entities, that may be confidential, proprietary, copyrighted and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
