Eeyup, that seems to do the trick! It complains about proper initialization
and Axis2 no longer logs to stdout, but I can serve soap again!
I now just need to find a way to harmonize the logging from Korma and the
logging that Axis2 provides. But that's an exercise left to the OP. :)
Thanks for
For the for the record and in case anyone has run into something similar,
I've fixed my problem and come to an understanding of it's nature...
First, the why:
As it turns out, Axis2, et. al defaults to yelling on the DEBUG log4j level
for it's activity logs. Thus, if the root appender says DEBUG
I'm pretty sure this is because of log4j.xml [1] in src directory of Korma.
I think it's take from here [2]. If you take a look at it, it sets root
debug level to debug.
Try creating your own configuration and pointing to it with command line
argument:
-Dlog4j.configuration=your_log4j.xml
What
Libraries probably shouldn't ship with a log4j configuration. The logging
configuration should be left entirely to the application IMO.
On 26 November 2011 19:37, Ivan Koblik ivankob...@gmail.com wrote:
I'm pretty sure this is because of log4j.xml [1] in src directory of
Korma. I think it's
So I'm trying to create a drop-in implementation of a SOAP webservice with
Clojure. Naturally I look into libraries that accomplish the different
bits. I need something to do SQL work with a relational db
(Kormahttps://github.com/ibdknox/korma,
check!) and I need to present a SOAP interface
