Hi, thanks for your reply. I took a different direction because I felt that writing a custom appender was overengineering a bit. I have gotten the Log4j2 properties to work in order to write the logs into a file and have written two utilities: one for reading the Logs from the abovementioned file and another one to make sure that each time I run that time the existing logs are removed (I would like to avoid that the test passes because of the same log entries are already present). The utility for reading the logs returns a boolean, so my Unit Test will simply assert whether the expected message matches the content of the line from the logs.
Thanks for your help, I. -- View this message in context: http://camel.465427.n5.nabble.com/Help-in-testing-a-custom-processor-tp5789934p5790009.html Sent from the Camel Development mailing list archive at Nabble.com.
