Thanx a lot.
How to Config the com.mydoain.database,
In the log4j.properties files, I use com.mydomain.database, it gives the
information of :
log4j:ERROR Could not find value for key or
log4j.logger.com.mydoain.database = INFO A2
log4j:ERROR Could not instantiate appender named " com.mydoain.da
You should really consider switching to Logger. All the old classes
(Category being one of them) have been deprecated (although only
unofficially, as they are not marked as such in javadocs) and are scheduled
to be removed sometime later this year.
That being said, the syntax using the Category c
How to Config the com.mydoain.database,
log4j:ERROR Could not find value for key or
log4j.logger.com.mydoain.database = INFO A2
log4j:ERROR Could not instantiate appender named " com.mydoain.database
=INFOA2".
-Original Message-
From: Steve Ebersole [mailto:[EMAIL PROTECTED]
Sent: 2
Thanks a lot
But I use the Category, how can I get the com.mydomain.database by
Category?
-Original Message-
From: Steve Ebersole [mailto:[EMAIL PROTECTED]
Sent: 2003年3月11日 19:35
To: Log4J Users List
Subject: Re: how to output to different files with different information
Can you includ
dl> It is also reasonable (and not that tough) to create Custom
dl> appenders that write directly to the vendors proprietary logger (I
dl> have one for WebLogic if you are interested)
I wouldn't mind seeing that. Thanks.
--
[EMAIL PROTECTED] (WJCarpenter)PGP 0x91865119
38 95 1B 69 C9 C6 3D 2
thanks for the clarification. I have always erred on the side of not
creating a connection that needs to be managed during bean passivation
i.e., the container should be providing this management thru a JCA/etc...
At 06:52 AM 3/11/2003 -0800, Nicholas wrote:
The spec is quite specific on t
Hi Andreas,
One factor you should certainly take into consideration is whether your deployment
environment is guaranteed to be JDK1.4 or higher. For example, many J2EE servers still
only support JDK 1.3.x so the logging APIs are unavailable.
Hope this helps
Keith
-Original Message-
Fr
Hi Andreas,
Check out the wiki page on this topic at:
http://nagoya.apache.org/wiki/apachewiki.cgi?Log4JProjectPages/Log4jvsJDKLogging
Just hang around this user list and the log4j developer list a while, and I
think you'll see enough exciting things going on to keep you wishing you
were using
Howdy,
It's kind of tough to take a guess at the whole java community, as it's
too huge. But among the mailing lists and communities I belong too,
there actually is a trend: novice developers use JDK 1.4. Better
developers use log4j. This happens because better/more experienced
developers appre
Hi,
We are currently starting Java development within our company. I am
confused as to whether we should use log4j or if we should consider
using the new logging API in JDK 1.4...
What factors should I take into consideration, and what is the Java
community doing?
Regards,
Andreas
The spec is quite specific on that note. You can act
as a socket client, but not a socket server:
24.1.2 Programming restrictions
.
.
An enterprise bean must not attempt to listen on a
socket, accept connections on a socket, or
use a socket for multicast.
The EJB architecture allows an enterpris
Nicholas is exactly correct. The spirit of the restriction is to restrict
file access from within the beans for the purpose of storing/retreiving
"business data". Business data being, for example, the state of an Entity
EJB. The reasoning is that filesystems do not support transactional
processi
Hi Michael,
Yes! I use log4j inside EJB containers all the time. You are correct
about the EJB specs ... in fact you should not open a Socket directly
either.. if you wanted to go this route you would need to make the Sockets
obtainable from the container by implementing a construct in the
J
It is not that black and white. The EJB specification
does not prohibit you from writing to a file.
EJB Spec 2.0
24.1.2 Programming restrictions
.
.
An enterprise bean must not use the java.io package
to attempt to access files and directories
in the file system.
The file system APIs are not we
Hi folks,
Just a quick query, as the EJB specification forbids you to write to a file
(which is what i want to do!)
why is it incorrect to do so? The alternatives are using SocketAppender
and JMSApender but how do
you write to a file using these? or put another way... can you?
Cheers,
_
Can you include your log4j.properties file?
Strictly based on the names of the files, it seems you want certain log
messages to go to A1 and all others to go to A2; then irregardless of
whether a message went to A1 or A2, also log it to A3. That correct?
In general that would be setup as:
log4j
16 matches
Mail list logo