cancel
Showing results for 
Search instead for 
Did you mean: 

v.2.5.0 external scripts fail "Could not find matching constructor"

SOLVED
JoostDG
Frequent Contributor

v.2.5.0 external scripts fail "Could not find matching constructor"

Hi,

 

I have some groovy scripts that work perfectly fine in ReadyAPI v.2.4.0, but after update to 2.5.0 they fail. The scripts can be found in my library just fine, but upon execution I get:

 

 ERROR: groovy.lang.GroovyRuntimeException: Could not find matching constructor for: scriptABC(com.eviware.soapui.impl.wsdl.panels.support.MockTestRunContext, org.apache.logging.log4j.core.Logger, com.eviware.soapui.impl.wsdl.panels.support.MockTestRunner)

 

My scriptABC.groovy :

 

import com.eviware.soapui.model.propertyexpansion.PropertyExpansionContext;
import org.apache.log4j.Logger;
import com.eviware.soapui.model.testsuite.TestRunner;

public class scriptABC
{
// Properties
def testRunner
def context
def log

// Constructor
scriptABC(PropertyExpansionContext context, Logger log, TestRunner testRunner)
{
this.context = context
this.log = log
this.testRunner = testRunner
}

// Methods
void Execute()
{...

}

1 ACCEPTED SOLUTION

Accepted Solutions
JoostDG
Frequent Contributor

Re: v.2.5.0 external scripts fail "Could not find matching constructor" - org.apache.log4j.Logger

Nevermind, found the solution.

 

Apparently

 

import org.apache.log4j.Logger

no longer covers it, it should be:

import org.apache.logging.log4j.core.Logger

 

That makes my scripts run again in 2.5.0.

View solution in original post

1 REPLY 1
JoostDG
Frequent Contributor

Re: v.2.5.0 external scripts fail "Could not find matching constructor" - org.apache.log4j.Logger

Nevermind, found the solution.

 

Apparently

 

import org.apache.log4j.Logger

no longer covers it, it should be:

import org.apache.logging.log4j.core.Logger

 

That makes my scripts run again in 2.5.0.

View solution in original post

New Here?
Join us and watch the welcome video:
Announcements
Top Kudoed Authors