Forum Discussion

Tindra's avatar
Tindra
Occasional Contributor
13 years ago

Version mismatch from external jars

Hi,

I currently have a problem regarding loading external jars into soapUI pro.

We have a jar that is build inhouse but depending on other jars (nested), in this case slf4j (version 1.6.1).
As the lib directory contains slf4j version of 1.5.8 there will be issues when trying to access classes within the external loaded jar.

Is there a way to resolve this issue or are all external jars loaded into same classpath?

3 Replies

  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    Icon for Alumni rankAlumni
    13 years ago
    Hi,

    I don't think soapUI is very tightly coupled to slf4j - have you tried replacing the included slf4j with the version you need?

    regards!

    /Ole
    SmartBear Software
  • Tindra's avatar
    Tindra
    Occasional Contributor
    13 years ago
    Thanks for the response!

    Well yes I have tried that and it solves slf4j issue, but then I fail on the next dependent jar.
    That could go on for a lot of common libraries, I don't really know how many right now.
    And I'm not to confident that it is the best solution to change versions of the jars that soapUI needs.
    That could result in a unstable soapUI client.

    And in the end it will result that all testers with a soapUI client also would need to replace the jars which complicates it even more.

    So I guess that the bin/ext and lib loading is tightly coupled to the same classpath?
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    Icon for Alumni rankAlumni
    13 years ago
    Hi,

    libraries in the ext folder are loaded into their own (shared) classloader - in your case I'm not sure if there is any other way to solve this then what you have already done.. what if you remove the slf4j library from the lib folder and only put your own in the ext folder!? (I'm not sure no how slf4j is being used anyway... )

    regards!

    /Ole
    SmartBear Software