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 is the default log level, Axis2 proceeds to constantly dump logs out to console. It seems broken in that state and no programmer in their right mind will go and try to digest a WSDL when the console is filling up with hundreds of lines of DEBUG spewing out with what looks like stack-traces. So the real answer was, I should have ignored the screaming logs and tried things anyway. You can fix it two ways, both of which involve providing your own log4j.xml: 1) You can set root log level to anything above DEBUG (INFO, for example.) 2) You can add two new loggers to contain the screaming server logs: "org.apache.axis2" and "org.apache.axiom" at, again at any log level above DEBUG. Hope this helps! -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
