Contributions
Re: Trouble loading XSD-compliant DOM-parser when using testRunner.sh vs. UI
I have now checked out the “Schema Compliance” assertion. I can’t find much documentation around so I don’t know what it’s actually supposed to validate. To me it seems it doesn’t validate the XML-content in the response. I have tried to supply some xsd’s in the grammar section which it seems to ignore. Regarding the original question I have finally figured out that also SoapUI cannot load the relevant schema factory. The message about this was hidden in a log and the assertion just showed that it worked. I’m back to square on and will test the groovy based xml validation outside SoapUI and play around with libraries thereafter.609Views0likes0CommentsRe: Trouble loading XSD-compliant DOM-parser when using testRunner.sh vs. UI
I wasn't sure, but looking further into it, it looks like that might be the case. I'll experiment with that, since this seems to be a more standardized way of doing the validation (requires a WADL defintion, so I'll see how much goes into that). Thx, Rune615Views0likes0CommentsRe: Trouble loading XSD-compliant DOM-parser when using testRunner.sh vs. UI
So I have a test step where I call a REST-function that returns some XML. In the test step I have added a "script assertion" that looks like this: def xml = org.apache.commons.io.IOUtils.toInputStream(messageExchange.responseContent, "utf-8") def xmlValidator = new XMLValidator(log) xmlValidator.validate(xml) The XMLValidator is a classI have defined in a groovy script (compiled into a jar). This works well when I use the green triangle (submit) button in my test. But if I use the testRunner.sh script I get the following (full) exception: Configuring log4j from [/Applications/SoapUI-5.4.0.app/Contents/java/app/bin/soapui-log4j.xml] 16:41:37,723 INFO [SoapUI] Adding [/Applications/SoapUI-5.4.0.app/Contents/java/app/bin/ext/RDFinedSoapUILib.jar] to extensions classpath 16:41:37,724 INFO [SoapUI] Adding [/Applications/SoapUI-5.4.0.app/Contents/java/app/bin/ext/saxon9pe.jar] to extensions classpath 16:41:37,724 INFO [SoapUI] Adding [/Applications/SoapUI-5.4.0.app/Contents/java/app/bin/ext/xercesImpl-xsd11-shaded-2.12-beta-r1667115.jar] to extensions classpath 16:41:37,724 INFO [SoapUI] Adding [/Applications/SoapUI-5.4.0.app/Contents/java/app/bin/ext/xml-apis-1.4.01.jar] to extensions classpath 16:41:37,955 INFO [DefaultSoapUICore] initialized soapui-settings from [/Users/runestilling/soapui-settings.xml] 16:41:38,525 INFO [PluginManager] 0 plugins loaded in 1 ms 16:41:38,526 INFO [DefaultSoapUICore] All plugins loaded 16:41:39,786 INFO [WsdlProject] Loaded project from [file:/Users/runestilling/Dropbox/Dokumenter/RDFined/Udvikling/SOAPUI/KLE-REST/KLE-REST-validering-soapui-project.xml] 16:41:39,790 INFO [SoapUITestCaseRunner] Running SoapUI tests in project [KLE-REST validator] 16:41:39,790 INFO [SoapUITestCaseRunner] Running TestCase [Handlingsfacetter] 16:41:39,794 INFO [SoapUITestCaseRunner] Running SoapUI testcase [Handlingsfacetter] 16:41:39,798 INFO [SoapUITestCaseRunner] running step [XML-validering] 16:41:39,923 DEBUG [HttpClientSupport$SoapUIHttpClient] Attempt 1 to execute request 16:41:39,923 DEBUG [SoapUIMultiThreadedHttpConnectionManager$SoapUIDefaultClientConnection] Sending request: GET /resources/kle/handlingsfacetter HTTP/1.1 16:41:43,290 DEBUG [SoapUIMultiThreadedHttpConnectionManager$SoapUIDefaultClientConnection] Receiving response: HTTP/1.1 200 16:41:43,294 DEBUG [HttpClientSupport$SoapUIHttpClient] Connection can be kept alive for 5000 MILLISECONDS 16:41:44,715 INFO [log] Validate begin 16:41:44,758 INFO [log] No SchemaFactory that implements the schema language specified by: http://www.w3.org/XML/XMLSchema/v1.1 could be loaded 16:41:44,759 INFO [log] [Ljava.lang.StackTraceElement;@3e2fc448 java.lang.IllegalArgumentException: No SchemaFactory that implements the schema language specified by: http://www.w3.org/XML/XMLSchema/v1.1 could be loaded at javax.xml.validation.SchemaFactory.newInstance(SchemaFactory.java:215) at javax.xml.validation.SchemaFactory$newInstance.call(Unknown Source) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:125) at XMLValidator.validate(XMLValidator.groovy:123) at XMLValidator$validate.call(Unknown Source) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:125) at Script1.run(Script1.groovy:4) at com.eviware.soapui.support.scripting.groovy.SoapUIGroovyScriptEngine.run(SoapUIGroovyScriptEngine.java:90) at com.eviware.soapui.impl.wsdl.teststeps.assertions.basic.GroovyScriptAssertion.assertScript(GroovyScriptAssertion.java:118) at com.eviware.soapui.impl.wsdl.teststeps.assertions.basic.GroovyScriptAssertion.internalAssertResponse(GroovyScriptAssertion.java:130) at com.eviware.soapui.impl.wsdl.teststeps.WsdlMessageAssertion.assertResponse(WsdlMessageAssertion.java:150) at com.eviware.soapui.impl.wsdl.teststeps.RestTestRequest.assertResponse(RestTestRequest.java:141) at com.eviware.soapui.impl.wsdl.teststeps.RestTestRequest.setResponse(RestTestRequest.java:128) at com.eviware.soapui.impl.wsdl.teststeps.RestTestRequestStep.run(RestTestRequestStep.java:810) at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.runTestStep(AbstractTestCaseRunner.java:211) at com.eviware.soapui.impl.wsdl.testcase.WsdlTestCaseRunner.runCurrentTestStep(WsdlTestCaseRunner.java:47) at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.internalRun(AbstractTestCaseRunner.java:138) at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.internalRun(AbstractTestCaseRunner.java:46) at com.eviware.soapui.impl.wsdl.support.AbstractTestRunner.run(AbstractTestRunner.java:128) at com.eviware.soapui.impl.wsdl.support.AbstractTestRunner.start(AbstractTestRunner.java:76) at com.eviware.soapui.impl.wsdl.testcase.WsdlTestCase.run(WsdlTestCase.java:594) at com.eviware.soapui.tools.SoapUITestCaseRunner.runTestCase(SoapUITestCaseRunner.java:573) at com.eviware.soapui.tools.SoapUITestCaseRunner.runRunner(SoapUITestCaseRunner.java:405) at com.eviware.soapui.tools.AbstractSoapUIRunner.run(AbstractSoapUIRunner.java:202) at com.eviware.soapui.tools.AbstractSoapUIRunner.run(AbstractSoapUIRunner.java:137) at com.eviware.soapui.tools.AbstractSoapUIRunner.runFromCommandLine(AbstractSoapUIRunner.java:112) at com.eviware.soapui.tools.SoapUITestCaseRunner.main(SoapUITestCaseRunner.java:122) 16:41:44,768 INFO [SoapUITestCaseRunner] Assertion [Script Assertion] has status VALID 16:41:44,769 INFO [SoapUITestCaseRunner] Finished running SoapUI testcase [Handlingsfacetter], time taken: 4354ms, status: FINISHED 16:41:44,770 INFO [SoapUITestCaseRunner] TestCase [Handlingsfacetter] finished with status [FINISHED] in 4354ms2.3KViews0likes2CommentsRe: Trouble loading XSD-compliant DOM-parser when using testRunner.sh vs. UI
First of all I didn't post the entire exception. But I'll do that. Regarding suggestions.Do you mean looking on the net? I'm very well aware of the meaning of the exception, and yes I did look on the net. Butsince mygroovy plugin work well when running the test from the SoapUI GUI I assume the problem is around testrunner.sh not being able to load the plugin dependent libraries properly. Any other ideas? /Rune2.4KViews0likes4CommentsRe: Trouble loading XSD-compliant DOM-parser when using testRunner.sh vs. UI
Hi I don't understand why this is off topic SoapUI.I have documented an odd behavior using SoapUI, where SoapUI does work running in one mode, and doing exactly the same thing is not working running in another mode. To me it seems like som sort of bug og at least an undocumented difference between running a SoapUI test from the UI and running it using the testrunner script. Regards, Rune2.4KViews0likes7CommentsTrouble loading XSD-compliant DOM-parser when using testRunner.sh vs. UI
Hi forum I haveadded a jar-file containing some groovy code that uses aSchemaFactory to validate an xml file using schema 1.1. For that purposes I have also added the special Xerces beta library that supports 1.1. This works fine when I run my test with assertion from the user interface. But - If I try the same test script using testRunner.sh it fails, even though it seems that the extension jars are loaded: 16:41:37,723 INFO [SoapUI] Adding [/Applications/SoapUI-5.4.0.app/Contents/java/app/bin/ext/RDFinedSoapUILib.jar] to extensions classpath 16:41:37,724 INFO [SoapUI] Adding [/Applications/SoapUI-5.4.0.app/Contents/java/app/bin/ext/saxon9pe.jar] to extensions classpath 16:41:37,724 INFO [SoapUI] Adding [/Applications/SoapUI-5.4.0.app/Contents/java/app/bin/ext/xercesImpl-xsd11-shaded-2.12-beta-r1667115.jar] to extensions classpath 16:41:37,724 INFO [SoapUI] Adding [/Applications/SoapUI-5.4.0.app/Contents/java/app/bin/ext/xml-apis-1.4.01.jar] to extensions classpath 16:41:37,955 INFO [DefaultSoapUICore] initialized soapui-settings from [/Users/runestilling/soapui-settings.xml] ... 16:41:44,715 INFO [log] Validate begin 16:41:44,758 INFO [log] No SchemaFactory that implements the schema language specified by: http://www.w3.org/XML/XMLSchema/v1.1 could be loaded 16:41:44,759 INFO [log] [Ljava.lang.StackTraceElement;@3e2fc448 java.lang.IllegalArgumentException: No SchemaFactory that implements the schema language specified by: http://www.w3.org/XML/XMLSchema/v1.1 could be loaded at javax.xml.validation.SchemaFactory.newInstance(SchemaFactory.java:215) at javax.xml.validation.SchemaFactory$newInstance.call(Unknown Source) What could the solution be to this? Regards, Rune2.6KViews0likes11CommentsmessageExchange.responseContent is always null on REST Request test step
Hi forum I want to to add a script assertion to a REST Request test step to be able to do an xml schema validation. First of all I need access to the response object, ie: def holder = groovyUtils.getXmlHolder( messageExchange.responseContent ) My problem is that no matter what I do themessageExchange.responseContent object is always null. Am I missing something obvious? Regards, RuneSolved1.1KViews0likes1CommentSoapUI 4.5.1 buggy windowing system on mac
I have used SoapUI on my mac in the past and am now running 4.5.1. Great tool but the windowing system on mac is buggy. Currently windows within the larger frame freeze in their positions. This means I can't move them around. Sometimes I can resize them, sometimes not. Sometimes I can suddenly move a window again after it has been stuck for a while. Seems to be related to other Mac users experience: viewtopic.php?f=13&t=12032&p=42215&hilit=mac#p42215 Regards, Rune12 years agoPlace ReadyAPI QuestionsReadyAPI Questions2.8KViews0likes5Comments