DO NOT REPLY [Bug 16229] - Convenience methods to cut object allocations in application code

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 16229] - Convenience methods to cut object allocations in application code

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 16229] - Convenience methods to cut object allocations in application code

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 29487] - new version does not respond

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 29487] - new version does not respond

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 29487] New: - new version does not respond

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

[GUMP@brutus]: logging-log4j/log4j-tests failed

local/gump/public/workspace/ant/dist/lib/ant-launcher.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-log4j/log4j-lf5-20040609.jar:

RE: JMSReceiver - chainsaw

From my googling this appears that it might be Classloader related. Ok, given that through Eclipse you can get it to work by simply having it on the general classpath, it should be possible to get this to work. What about if you try and put the Weblogic.jar file in the %CLASSPATH% environment va

RE: JMSReceiver - chainsaw

Hmmm, I wonder if the weblogic.jar needs to be signed? But then I don't think it needs to be when just running outside Web start. I'll have to do some googling and get back to you. Looks like JMS is going to be my nemisis of the month. cheers, Paul Smith On Wed, 9 Jun 2004, Stephen Pain wrote

cvs commit: logging-log4j/tests/input/db oracle.properties.sample

ceki2004/06/09 08:22:42 Modified:src/java/org/apache/log4j/db/dialect oracle.sql OracleDialect.java tests/input/db oracle.properties.sample Log: Doc improvements Revision ChangesPath 1.10 +1 -0 logging-log4j/src/java/or

Re: Oracle Tests

Thanks James. So we now have DBAppender/DBReceiver tested for PostgreSQL, MySQL, Oracle and HSQLDB. DBAppender/DBReceiver already has support for DB2 and MsSQL but we still need to run the tests with DB2 and MsSQL. I don't expect there to be any problems. Interestingly enough, Oracle was the least

Oracle Tests

Title: Oracle Tests Ceki and I were able to get Oracle database tests created and passing.  He did most of the work -- I mostly just ran test after he made code changes.  If anyone is interested I could email the results.  I ran it using the jdbc80520-nt.zip driver to a Oracle9i Release 9.2.0.

RE: JMSReceiver - chainsaw

Hi Paul, Putting the weblogic.jar in JAVA_HOME/lib/ext as you suggested allowed me to start chainsaw, but I wasn't getting any events via the JMSReceiver (not seeing any exceptions in the console log either). So I tried running from eclipse, and got the nasty error below. I tried removing we

cvs commit: logging-log4j/tests/input/db oracle.properties.sample

ceki2004/06/09 07:01:58 Added: tests/input/db oracle.properties.sample Log: Property sample file for Oracle. Revision ChangesPath 1.1 logging-log4j/tests/input/db/oracle.properties.sample Index: oracle.properties.sample ==

cvs commit: logging-log4j/tests/input/db append-with-drivermanager1.xml read-with-drivermanager1.xml

ceki2004/06/09 06:53:19 Modified:tests/input/db append-with-drivermanager1.xml read-with-drivermanager1.xml Log: The property name "url" seems to be DriverManager imposed even for Oracle. Revision ChangesPath 1.4 +1 -1 logging-log4j/

RE: JMSReceiver - chainsaw

ok, I am just applying your patch now (by hand, but that's just coz I can't work out why the patch doesn't work). Soon I will check in the change to cvs, will you be able to verify by trying it out with the ant version? cgheers, Paul On Wed, 9 Jun 2004, Stephen Pain wrote: here's the unified di

RE: JMSReceiver - chainsaw

can't you put the weblogic jar in the JAVA_HOME\lib\ext ? cheers, Paul Smith On Wed, 9 Jun 2004, Stephen Pain wrote: Thanks Paul - now I just need to work out how to add the weblogic.jar to the classpath so that it's picked up by chainsaw. Do you know how I can do this? Can't start chainsaw at th

RE: JMSReceiver - chainsaw

Thanks Paul - now I just need to work out how to add the weblogic.jar to the classpath so that it's picked up by chainsaw. Do you know how I can do this? Can't start chainsaw at the moment because I'm getting this error: java.lang.NoClassDefFoundError: javax/jms/MessageListener - which is to b

RE: JMSReceiver - chainsaw

I have made the changes, and signed and uploaded. Now just crossing fingers. I have added your name to the JMSReceiver java file, I hope you don't mind. cheers, Paul Smith On Wed, 9 Jun 2004, Stephen Pain wrote: here's the unified diff - sorry for the delay... Cheers, Stephen $ diff -u JMSRece

cvs commit: logging-log4j/src/java/org/apache/log4j/chainsaw/help release-notes.html

psmith 2004/06/09 02:32:57 Modified:src/java/org/apache/log4j/chainsaw/version VersionManager.java src/java/org/apache/log4j/chainsaw/help release-notes.html Log: Updated release notes and version. Revision ChangesPath 1.7 +1

cvs commit: logging-log4j/src/java/org/apache/log4j/net JMSReceiverBeanInfo.java

psmith 2004/06/09 02:32:40 Added: src/java/org/apache/log4j/net JMSReceiverBeanInfo.java Log: This adds the missing BeanInfo class for the JMSReceiver so only the relevant properties appear in the buit-in Receiver editor of Chainsaw. Revision ChangesPath 1.1

cvs commit: logging-log4j/src/java/org/apache/log4j/net JMSReceiver.java

psmith 2004/06/09 02:31:33 Modified:src/java/org/apache/log4j/net JMSReceiver.java Log: Applied a patch supplied by Stephen Pain that allows for a property that is used to load a jndi.properties file, which is required for some J2EE servers such as weblogic. This is not the

cvs commit: logging-log4j build.xml

psmith 2004/06/09 02:29:17 Modified:.build.xml Log: This change gets around the condition where you use the 'j2ee.jar', which includes the classes needed for the JMS side of things, and SOME of the classes that JMX needs. Otherwise the JMX check will pass, but won't com

RE: JMSReceiver - chainsaw

here's the unified diff - sorry for the delay... Cheers, Stephen $ diff -u JMSReceiver.java.old JMSReceiver.java --- JMSReceiver.java.old2004-06-07 10:38:01.186774200 +0100 +++ JMSReceiver.java2004-06-07 10:35:27.096615800 +0100 @@ -7,6 +7,10 @@ package org.apache.log4j.net; +impo