kbertran99
New Contributor
Joined 4 years ago
User Profile
User Widgets
Contributions
Re: external libraries management issue
KarelHusa, krsfst first of all, thank you for your advice. I have finally resolved my issue. Thanks to AI, I understood where my mistake came from. The soapUI application has no issue. The external libraries are correctly imported at the application’s launch. Indeed, I do have logs of the type ‘INFO: Adding […jar] to extension classpath’ following the application’s launch. However, one of them uses (or imports) an org.apache.log4j library which is deprecated. Hence the error message ‘Could not initialize class …’. To fix my issue, I have therefore updated the external library so that it no longer references the deprecated library, but the one supported by soapUI (org.apache.logging.log4j).32Views0likes0CommentsRe: external libraries management issue
Thanks for your feedback KarelHusa, As reported by krsfst, my jarfiles are not located into "C:\Program Files\SmartBear\SoapUI-5.7.0\bin\ext\" folder, but into "c:\Users\username\AppData\Local\Programs\SmartBear\SoapUI-5.7.0\bin\ext\". My Operating System is : "Windows 10 Pro" (version 21H2, build 19044.1466) Best regards, Karl561Views1like0Commentsexternal libraries management issue
Hi, i am currently using soapUI 5.6.0. Last week I upgraded throught 5.7.0 and I noticed a regression regarding the external librairies management (i was facing to an error message like "could not initialize class ..."). I could reproduce this issue with soapUI 5.6.1 version. So, I rollback to the previous version soapUI (5.6.0), and my soapUI project can initialise class coming from external library (located in {soapUI directory}/bin/ext). Please, is it possible to confirm this issue and fix it? Best regards, Karl730Views1like4Comments