ContributionsMost RecentMost LikesSolutionsSoapUI-5.5.0: ExceptionInInitializerError during configuration of log4j from soapui-log4j.xml Hello community, I'm having issues while upgrading to SoapUI 5.5.0: I'm getting an ExceptionInInitializerError exception while configuring log4j from soapui-log4j.xml. So far the answer i've found are related to the issue reported onhttps://community.smartbear.com/t5/SoapUI-Open-Source/SoapUI-5-4-0-ExceptionInInitializerError-during-new-settings/m-p/156913#M26056but now i'm not getting that error anymore (I tried the propsed soution and replaced the soapui-settings.xml and now i'm ok with that). Can somebody please help me on this? FYI: I'm running SoapUI 5.2.0 and it's working fine. Re: SoapUI Pro Jenkins Plug-ins Passing Parameters Helloashu248, I'm kind of dealing with the same issue: I wanna pass soapui an excel file through Jenkins, I've configured maven file like this: <groupId>com.smartbear.soapui</groupId> <artifactId>soapui-maven-plugin</artifactId> <version>5.1.3</version> <configuration> <projectFile>${soapuiHome}\workspace\projects\${soapuiProjectFile}</projectFile> <testSuite>${soapuiTestSuite}</testSuite> <testCase>${soapuiTestCase}</testCase> <projectProperties> <value>HostIP=${hostIP}</value> <value>HostPort=${hostPort}</value> <!-- override EndPointHost (used in projects with no Launcher)--> <value>EndPointHost=http://${hostIP}:${hostPort}</value> <value>SoapUIHome=${soapuiHome}\bin\</value> <value>Jenkins=Y</value> <value>dataSource=${dataSource}</value> </projectProperties> where<value>dataSource=${dataSource}</value> is the field for the File parameter. Now when I check those props in SoapUI context it's only a String. I tried getting (from SoapUI) Jenkins workspace and then the .xlsx file but so far no luck because of an known issue for that. Can you please help me? Re: Validate xml response with an xsd file. Hellosnand, No, I haven't. Sorry. Re: Properties with special characters thanksJHunt, Find attached the version I'm using and yes, will send you the project ASAP. Again thank you for helping me. Re: Properties with special characters I think it's removing all backslashes from the string, maybe it's thinking is a path? Re: Properties with special characters HeyHimanshuTayal Thank you so much for replying. Here are the screenshots: 1. property.png: you will see the value with the slashes in a property step 2. xml.png: shows where I reference that property from MyProperties property step 3. RQ.png: shows how the request gets buit when run that soap step. As you can see, the slashes got removed somehow and I don't know why? Properties with special characters Hello team, I'm getting in a response this: <Key>pB8PD+pN8ALD*qB9KDJ+DB8DBD?K/3*BV9/321*NA9///8*CA96107*SN9LDEN*QL97563*EL931*QM97877*Q/9VNV+MQ80*OV9?CR+PA857+BS88370+RL8007.+PS88/7*ER9706+PQ87~h9DAA~IYz o_w 9Y!?CR![+ rcfkdlsq!8Zy!gc 9 A/!*!daa!8!CCC@J02!~i\~i\~J9DKVO*flxKey</Key> *Note the red slashes And I'm putting this value in a property (MyProperties) step but when I try to grab that value in a later request through ${MyProperties#Key} <OldKey>${MyProperties#Key}</OldKey> I get this: <OldKey>pB8PD+pN8ALD*qB9KDJ+DB8DBD?K/3*BV9/321*NA9///8*CA96107*SN9LDEN*QL97563*EL931*QM97877*Q/9VNV+MQ80*OV9?CR+PA857+BS88370+RL8007.+PS88/7*ER9706+PQ87~h9DAA~IYz o_w 9Y!?CR![+ rcfkdlsq!8Zy!gc 9 A/!*!daa!8!CCC@J02!~i~i~J9DKVO*flxKey</OldKey> * Note now without the slashes Why this happens and what would be the workaround in this situation? Re: Validate xml response with an xsd file. Hello nmrao, I have an issue when using an xsd file that contains this: <xsd:include schemaLocation="edist_commontypes.xsd"/> <xsd:include schemaLocation="aidm_commontypes.xsd"/> I mean, it "includes" another xsd (reference). How to deal with this? I'm trying to validate an xml file using this xsd file (that also includes reference to another xsd). Re: soap ui groovy debug Thank younmraofor your answer. Re: soap ui groovy debug Thank you so muchwujianyyfor your answer, in my case I have a mix of variant 1 and 2, that's why I was looking for a solution (non Pro version, of course). I think I'd separate the soapui logic from the groovy script in order to debug the latter one.