Hi,
This is off subject but it would be great if the logger could output XML.
Eric :-)
Olivier Richaud wrote:
> Does this mean that Jonas logger will be tightly coupled to Enhydra
> enterprise server? I'm a Jonas user but not a Enhydra user because I only
> need Jonas. If I need Enhydra only because I need a performant logger, this
> is bad news.
>
> I posted my own logger which both handles asynchronous and synchronous
> logging. Each instanciated logger is associated to a distinct log file. Here
> is a sample output in its Jonas version:
>
> [jeu. juil. 06 17:57:13 2000] [err] [DB_ALL] this is a sample test (err)
> [jeu. juil. 06 17:57:13 2000] [err] [DB_ALL] this is a sample test (errln)
> [jeu. juil. 06 17:57:13 2000] [err] [DB_ALL] java.lang.Exception: this is a
> sample exception (errln)
> at test2.main(test2.java, Compiled Code)
> [jeu. juil. 06 17:57:13 2000] [err] [DB_ALL] java.lang.Exception: this is a
> sample exception (errln, true)
> at test2.main(test2.java, Compiled Code)
>
> Olivier Richaud
> CSTB
> office: +33 4 93 95 67 24
> mobile: +33 6 87 52 53 17
> www: http://cic.cstb.fr
> ----- Message d'origine -----
> De : Wayne Stidolph <[EMAIL PROTECTED]>
> � : 'ejb-container-group' <[EMAIL PROTECTED]>
> Envoy� : jeudi 6 juillet 2000 17:34
> Objet : RE: Logging / Tracing (?)
>
> > When JOnAS is integrated into Enhydra Enterprise, it can take advantage of
> > the Enhydra logging facilities (as can application-level code). At the
> > applications level you will get an independent logging instance and write
> to
> > it. That applications log is separate from other logs. The logging
> instance
> > will support multiple categories and off-host logging (by sending messages
> > on JMS topics). If you want each bean to open its own log, that would be
> up
> > to you.all sorts of stuff - see
> > http://www.enhydra.org/software/enhydraEnterprise/eeVer4.html#logging for
> an
> > initial discussion of the goal and structure.
> >
> > What do you mean by "better distinction between threads" and "better
> > distinction between beans"?
> >
> > This is not near the bottom of the TODO list; it will happen - later in
> the
> > summer. We have a reasonable logging facility in place in Enhydra 3.0 now,
> > the kernel logging in Enhydra Enterprise 4 works now, and we keenly
> > recognize that effective logging will have to be in Enhydra Enterprise.
> >
> > If anyone wants to accelerate the building of the logging service for
> > Enterprise, then check in with the Architecture Working Group
> > (http://www.enhydra.org/community/workingGroups/Architecture.html), submit
> > detail suggestions, sign up to build the thing, etc...
> >
> > Wayne Stidolph / Lutris Technologies
> >
> >
> > -----Original Message-----
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]On Behalf Of Markus
> Blaurock
> > Sent: Wednesday, July 05, 2000 7:03 AM
> > To: 'ejb-container-group'
> > Subject: Logging / Tracing (?)
> >
> > It would be nice to have a better
> > logging / tracing mechanism in Jonas/Enhydra Ent.,
> > wouldn't it ?
> >
> > It would be great to have logging output
> > send to a remote machine, different categories,
> > better distinction between threads and
> > distinction between beans...
> >
> > What are the plans for this ?
> > Maybe these things are at the very bottom
> > of the TODO-List...
> >
> > Has somebody thought about integrating
> > a 3party class-library like log4j
> > (www.log4j.org) ?
> >
> > Especially for developing prototype apps
> > with Jonas this would be a great help...
> >
> > --
> > markus
> >
> > ----
> > This list is cross-posted to two mail lists. To unsubscribe,
> > follow the instructions below for the list you subscribed to.
> > For objectweb.org: send email to [EMAIL PROTECTED] and
> > include in the body of the message "unsubscribe ejb-container-group".
> > For enhydra.org: send email to [EMAIL PROTECTED] and include
> > in the body of the message "unsubscribe ejb-container-group".
> >
> > ----
> > This list is cross-posted to two mail lists. To unsubscribe,
> > follow the instructions below for the list you subscribed to.
> > For objectweb.org: send email to [EMAIL PROTECTED] and
> > include in the body of the message "unsubscribe ejb-container-group".
> > For enhydra.org: send email to [EMAIL PROTECTED] and include
> > in the body of the message "unsubscribe ejb-container-group".
> >
>
> ----
> This list is cross-posted to two mail lists. To unsubscribe,
> follow the instructions below for the list you subscribed to.
> For objectweb.org: send email to [EMAIL PROTECTED] and
> include in the body of the message "unsubscribe ejb-container-group".
> For enhydra.org: send email to [EMAIL PROTECTED] and include
> in the body of the message "unsubscribe ejb-container-group".
----
This list is cross-posted to two mail lists. To unsubscribe,
follow the instructions below for the list you subscribed to.
For objectweb.org: send email to [EMAIL PROTECTED] and
include in the body of the message "unsubscribe ejb-container-group".
For enhydra.org: send email to [EMAIL PROTECTED] and include
in the body of the message "unsubscribe ejb-container-group".