Bug 38513 - [PATCH] Suggested unit test for JMSAppender
Summary: [PATCH] Suggested unit test for JMSAppender
Status: NEW
Alias: None
Product: Log4j - Now in Jira
Classification: Unclassified
Component: Appender (show other bugs)
Version: 1.3alpha
Hardware: Other other
: P2 normal
Target Milestone: ---
Assignee: log4j-dev
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-02-05 01:09 UTC by Paul Smith
Modified: 2006-02-04 16:13 UTC (History)
0 users



Attachments
jndi.properties to define JMS connection/topic details for ActiveMQ (needs to be in root of test classpath) (407 bytes, text/plain)
2006-02-05 01:12 UTC, Paul Smith
Details
JMSAppenderTest class (2.94 KB, text/plain)
2006-02-05 01:12 UTC, Paul Smith
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Paul Smith 2006-02-05 01:09:32 UTC
The following attached patch can test the functionality of the JMSAppender.

It uses ActiveMQ JMS, a ASL licensed JMS implementation (and currently in
incubator to join the ASF as a project).

This test case requires the following jars to be added to the test classpath:

* activemq-3.2.1.jar
* commons-logging (api or implementation jar)
* concurrent.jar 
* the JMS spec jar (easily grabbed from geronimo-spec-j2ee-management-1.0-rc4.jar)

All of these can be easily downloaded from the ActiveMQ distribution here:

http://www.activemq.org/Download

the patch uses a jndi.properties in the root of the test classpath.  I'm not
sure whether that has any other affect on any other test within the log4j tests.
Comment 1 Paul Smith 2006-02-05 01:12:00 UTC
Created attachment 17590 [details]
jndi.properties to define JMS connection/topic details for ActiveMQ (needs to be in root of test classpath)
Comment 2 Paul Smith 2006-02-05 01:12:32 UTC
Created attachment 17591 [details]
JMSAppenderTest class
Comment 3 Paul Smith 2006-02-05 01:13:09 UTC
This issue relates to Bug #38512