sdeboy 2004/05/21 22:55:02
Modified:src/java/org/apache/log4j/chainsaw
ChainsawToolBarAndMenus.java
src/java/org/apache/log4j/chainsaw/help release-notes.html
Log:
Removed jdk1.4-specific code (shift_down_mask to shift_mask). Chainsaw can now
sdeboy 2004/05/21 22:26:12
Modified:src/java/org/apache/log4j/chainsaw LogPanel.java
src/java/org/apache/log4j/chainsaw/help release-notes.html
Log:
Changed how 'scroll to bottom' is activated and deactivated.
Now, scrolling occurs only if 'scroll to bottom' is s
ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-xalan2.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/logging-
sdeboy 2004/05/21 18:21:58
Modified:src/java/org/apache/log4j/chainsaw/help release-notes.html
Log:
fixed typo
Revision ChangesPath
1.8 +1 -1
logging-log4j/src/java/org/apache/log4j/chainsaw/help/release-notes.html
Index: release-notes.html
===
sdeboy 2004/05/21 18:17:02
Modified:src/java/org/apache/log4j/xml UtilLoggingXMLDecoder.java
XMLDecoder.java
src/java/org/apache/log4j/chainsaw FileLoadAction.java
ChainsawAppenderHandler.java
src/java/org/apa
> I love this. However, there is one usability issue. Assume you select
> the
> first logger, by the time you want to select the second logger, the
> events
> disappear leaving you with only the events of the first logger. Do you
> see
> what I mean?
Remember that the filters are applied to a
Ceki Gülcü wrote:
Other errors included the usage of the javax.rmi.PortableRemoteObject
class which is not part of JDK 1.2. This problem affects only the
o.a.l.db.JNDIConnectionSource class.
Ceki,
The PortableRemoteObject class should be available in J2EE distributions
or RMI/JNDI distributions.
The display filtering process works like this:
1. Filter based on the logger tree 'focus on' and 'exclude' settings
2. Refine the results from #1 based on the 'refine focus' field
Scott
-Original Message-
From: Ceki Gülcü [mailto:[EMAIL PROTECTED]
Sent: Friday, May 21, 2004 1:07 PM
To: L
At 09:13 PM 5/21/2004, you wrote:
There are two choices off the top of my head for supporting the display of
multiple loggers at once:
- in the logger tree: disable individual loggers you'd like to exclude in
a hierarchy, and then focus on the higher level hierarchy, OR
That doesn't sound practi
I'm sorry, this can be a little confusing.
The tab identifier doesn't require an expression - but identifiers that are looked up
as events are seen and routed based on the values of those replaced identifiers -
The 'create custom expression logpanel' does require a valid expression (something
Thanks for the detailed explanations Scott. Is this explanation available
somewhere easily accessible by Joe user? Did I miss it?
I tried using "create custom expression LogPanel" with PROP.hostname and
also just LEVEL. Each time I got an error , for example, "Unable to add tab
using expression
There are two choices off the top of my head for supporting the display of multiple
loggers at once:
- in the logger tree: disable individual loggers you'd like to exclude in a hierarchy,
and then focus on the higher level hierarchy, OR
- in the 'refine focus' field, define an expression explici
The 'tab identifier' field in the application-wide preferences window controls how
events are routed to unique tabs. The syntax used in this identifier is the same
expression syntax used by color rule expressions and the 'refine focus' field..
As events are received, the tab identifier expressi
Thanks, Ceki
We'll try to get the 'view release notes' popup to occur after the configuration popup
is dismissed..
-Original Message-
From: Ceki Gülcü [mailto:[EMAIL PROTECTED]
Sent: Friday, May 21, 2004 11:25 AM
To: [EMAIL PROTECTED]
Subject: Freeze up at startup
Hello,
When I ran
ceki2004/05/21 11:45:07
Modified:src/java/org/apache/log4j/helpers Constants.java
src/java/org/apache/log4j/db DBReceiver.java
ConnectionSource.java
DataSourceConnectionSource.java DBAppender.java
src/java/
Hi again,
The automatic direction of events to various panels is a very powerful
feature. Is this feature documented somewhere?
The capability to focus on a logger is also very useful. Is it possible to
focus on multiple loggers at once? It looked as if that was not the case.
Thanks in advance,
Hello,
When I ran chainsaw recently it gave me a warning about format changes in
the latest version. This is very considerate except that the dialog box
showing the warning freezes up. It's not easy to reproduce this problem
because it happens only once. As soon as you modify your preferences an
ceki2004/05/21 09:13:43
Modified:src/java/org/apache/log4j/db DBReceiver.java DBAppender.java
Log:
It is so much better when connections are closed. :-)
Revision ChangesPath
1.8 +15 -2 logging-log4j/src/java/org/apache/log4j/db/DBReceiver.java
Index: DB
ceki2004/05/21 08:12:09
Modified:src/java/org/apache/log4j/db DBReceiver.java
Log:
Given that LoggingEvent properities are Strings and not general Objects, and
given that in future versions of DBAppender events may be written in
batches instead of one by one, there is not m
ceki2004/05/21 08:07:06
Modified:tests/src/java/org/apache/log4j/util SunReflectFilter.java
Log:
Required to have unit tests succeed under JDK 1.3 as well as 1.4.
Revision ChangesPath
1.5 +5 -1
logging-log4j/tests/src/java/org/apache/log4j/util/SunReflectF
ceki2004/05/21 08:05:45
Modified:tests/src/java/org/apache/log4j/xml XMLLayoutTestCase.java
Log:
Required to have unit tests succeed under JDK 1.3 as well as 1.4.
Revision ChangesPath
1.12 +1 -0
logging-log4j/tests/src/java/org/apache/log4j/xml/XMLLayoutTes
ceki2004/05/21 04:31:48
Modified:.build.properties.sample build.xml
Log:
Made JNDI API are required dependency for the build.core target. JNDI API
is part of JDK 1.3 and later so should not be a serious hurdle.
Revision ChangesPath
1.17 +22 -13loggi
ceki2004/05/21 03:50:39
Modified:src/java/org/apache/log4j/xml XMLDecoder.java
src/java/org/apache/log4j/db JNDIConnectionSource.java
Log:
The javax.rmi.PortableRemoteObject is not part of JDK 1.2. Stopped
using it in JNDIConenctionSource.
In o.a.l.xm
Hi again,
Compiling log4j under JDK 1.2 results remarkably few erros:
build.core:
[javac] Compiling 7 source files to
C:\home\cgu\ASF\logging-log4j\dist\classes
[javac]
C:\home\cgu\ASF\logging-log4j\src\java\org\apache\log4j\net\SocketHubReceiver.java:222:
Method getListeners(java.lang.C
Good morning,
I am happy to report that when building log4j under JDK 1.3, there just one
error.
chainsawCheck:
[echo] Chainsaw dependant libraries present.
build.chainsaw:
[javac] Compiling 115 source files to
C:\home\cgu\ASF\logging-log4j\dist\classes
[javac]
C:\home\cgu\ASF\logg
psmith 2004/05/21 03:13:30
Modified:src/java/org/apache/log4j/chainsaw/vfs VFSPlugin.java
Log:
Looks like there was a race condition between the child directory locator thread
that updates the Tree and the child file locator thread that populates the table.
Properly synchr
ceki2004/05/21 02:24:51
Modified:.build.properties.sample build.xml
Log:
Trying to build on JDK 1.3 and 1.2
Revision ChangesPath
1.16 +22 -1 logging-log4j/build.properties.sample
Index: build.properties.sample
==
27 matches
Mail list logo
