blob: ec9375dce332a89ace5a89f2ad9f70519f3ed740 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
|
/*
* Copyright (c) 2016 Brocade Communications Systems, Inc. and others. All rights reserved.
*
* This program and the accompanying materials are made available under the
* terms of the Eclipse Public License v1.0 which accompanies this distribution,
* and is available at http://www.eclipse.org/legal/epl-v10.html
*/
package org.opendaylight.aaa.shiro;
import ch.qos.logback.classic.spi.LoggingEvent;
import ch.qos.logback.core.AppenderBase;
import java.util.List;
import java.util.Vector;
/**
* A custom slf4j <code>Appender</code> which stores <code>LoggingEvent</code>(s) in memory
* for future retrieval. This is useful from inside test resources. This class is specified
* within <code>logback-test.xml</code>.
*
* @author Ryan Goulding (ryandgoulding@gmail.com)
*/
public class TestAppender extends AppenderBase<LoggingEvent> {
/**
* stores all log events in memory, instead of file
*/
private List<LoggingEvent> events = new Vector<>();
/**
* Since junit maven & junit instantiate the logging appender (as provided
* by logback-test.xml), singleton is not possible. The next best thing is to track the
* current instance so it can be retrieved by Test instances.
*/
private static volatile TestAppender currentInstance;
/**
* keeps track of the current instance
*/
public TestAppender() {
currentInstance = this;
}
@Override
protected void append(final LoggingEvent e) {
events.add(e);
}
/**
* Extract the log.
*
* @return the in-memory representation of <code>LoggingEvent</code>(s)
*/
public List<LoggingEvent> getEvents() {
return events;
}
/**
* A way to extract the appender from Test instances.
*
* @return <code>this</code>
*/
public static TestAppender getCurrentInstance() {
return currentInstance;
}
}
|
