I guess using JMS is good for having a single logging repository. This way
you will ease monitoring, hence it will provide a higher level of
maintainability. Not a bad idea!

Christophe
SCEA

> That's fine but use the Log4j JMS appender rather than the file
> appender. Use this appender to write to a queue and have your logging
> server on the other end of the queue.
>
> -----Original Message-----
> From: Vadlamudi, Ranga Rao (Cognizant) [mailto:VRanga@(protected)]
> Sent: 29 September 2003 11:53
> To: J2EEPATTERNS-INTEREST@(protected)
> Subject: Re: [J2EEPAT-INT] How does ejbs do logging?
>
>
> Currentlyiam using Log4j directly in EJB's and i have not encountered
> any problems ...
>
> -----Original Message-----
> From: BOWMAN, James [mailto:James.Bowman@(protected)]
> Sent: Monday, September 29, 2003 3:44 PM
> To: J2EEPATTERNS-INTEREST@(protected)
> Subject: Re: How does ejbs do logging?
>
>
> Log to the database. Accessing the file system is not allowed within
> the EJB container. If you really wish to have a log file, the code that
> writes to the file must run outside of the container. EJBs can then
> make calls to this "logging server" using RMI, sockets or JMS.
>
> -----Original Message-----
> From: peng wang [mailto:wp0@(protected)]
> Sent: 26 September 2003 15:56
> To: J2EEPATTERNS-INTEREST@(protected)
> Subject: [J2EEPAT-INT] How does ejbs do logging?
>
>
> Hi,
>
> I heard of the ejbs cannot access local file system,
> is it true? if true, I wonder how ejbs do logging
> into files such as printing debug info.
>
> In addition, if there are two session beans which are
> packed in two different jar files, the two jar files
> are deployed within one same ejb container. Can one
> session call the other by using local interface?(The
> local interface has been implemented.)
>
> Thanks for help!
>
> __________________________________
> Do you Yahoo!?
> The New Yahoo! Shopping - with improved product search
> http://shopping.yahoo.com
>
> ====================================================================
> Companion Site: http://www.corej2eepatterns.com
> J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
> List Archive:
> http://archives.java.sun.com/archives/j2eepatterns-interest.html
> Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to
> listserv@(protected)
>
> ---
> Incoming mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.518 / Virus Database: 316 - Release Date: 11/09/2003
>
> ====================================================================
> Companion Site: http://www.corej2eepatterns.com
> J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
> List Archive:
> http://archives.java.sun.com/archives/j2eepatterns-interest.html
> Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to
> listserv@(protected)
>
> ====================================================================
> Companion Site: http://www.corej2eepatterns.com
> J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
> List Archive:
> http://archives.java.sun.com/archives/j2eepatterns-interest.html
> Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to
> listserv@(protected)
>
> ---
> Incoming mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.518 / Virus Database: 316 - Release Date: 11/09/2003
>
> ====================================================================
> Companion Site: http://www.corej2eepatterns.com
> J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
> List Archive:
> http://archives.java.sun.com/archives/j2eepatterns-interest.html
> Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to
> listserv@(protected)

====================================================================
Companion Site: http://www.corej2eepatterns.com
J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
List Archive: http://archives.java.sun.com/archives/j2eepatterns-interest.html
Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to listserv@(protected)