SoapUI overwrites and closes log4j settings

Hi all,
I just register on this forum to add a reply to this post

thanks redfish4ktc2 for your tip ! this help me.


I had exactly the same problem: while using SoapUITestCaseRunner or WsdlProject,
=> SoapUI Logger take the hand on Log4j configuration, and I loose my log4j output and related console output...


After a SoapUI run() call, any logs are only keeped in the "soapui.log" file.
(following //soapui-4.5.1.jar:/com/eviware/soapui/resources/conf/soapui-log4j.xml configuration);


For my project, I'm using a "log4j.properties" file and not an xml one.
I found a workaround to keep (ONLY) my own log4j configuration by setting an empty log4j xml config file for soapUI.

It would be great to update soapui to add a toggle flag to do this for me :
- for example : "soapui.log4j.keepcurrentconfig" (true|false) system property [default:false]
=> if set to true, then soapui doesn't overrite the current log4j configuration
(I'm not sure about the flag's name )


workaround example :

    System.setProperty("soapui.log4j.config","target/test-classes/soapui-log4j.xml");
    LOG.info("play wsdl SoapUI Project :" +soapUiResource);
      SoapUITestCaseRunner runner = new SoapUITestCaseRunner();
      runner.setProjectFile(soapUiResource);
      runner.setPrintReport(true);
      runner.setOutputFolder("target/");
      runner.runRunner();
    LOG.info("my log after a run() or runRunner() call..");

an empty soapui-log4j.xml:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE log4j:configuration SYSTEM "log4j.dtd">
<log4j:configuration xmlns:log4j="http://jakarta.apache.org/log4j/" debug="false">  
</log4j:configuration>

regards

force soapui to use your log4j configuration file by setting the "soapui.log4j.config" system property to the path to your log4j file

nice if my tip helps!
if your log4j propertes file is available in a directory, you can directly tell soapui to use it with something like

System.setProperty("soapui.log4j.config","path/to/your/log4j.properties");

I had sax errors while using "log4j.properties" as value
Regards

yes you are right, it only works with a log4j xml file.