mindgnat
Occasional Contributor
Joined 13 years ago
User Profile
User Widgets
Contributions
Re: [R]Missing operation for soapAction [] and body element, moc
Thanks for taking the time to post this solution. However, that had no effect on my Community Edition 5.2.1 version of SoapUI. The same problem persists. Has anyone else tried this solution and gotten past the problem or does it still remain after this change?11KViews0likes0CommentsRe: Is SoapUI still being supported?
I'm wondering if SmartBear is supporting SoapUI any more. Your question was asked a month ago and no one has bothered to reply. I ended up backtracking to SoapUI 5.2.1 in order to get maven-initiated testing working. It took me forever to figure out the exact POM configuration that worked. SmartBear's documentation doesn't provide an example POM, which would really save everyone a lot of time. I have attached my working POM. I had to remove ".soapuios" from my home directory. SoapUI will replace it when you re-start it. <testFailIgnore>true</testFailIgnore> will cause mvn to return exit code 0 (BUILD SUCCESS) if any tests fails. Delete this line if you want it to return exit code 1 (BUILD FAILURE) when any test fails. HTH3.5KViews1like4CommentsExceptionInInitializerError
SoapUI 4.5.1 Eclipse Juno JDK 1.6 Win 7SP1, 64b JUnit 4.10 I can run the SoapUI app but I'm getting an error when I set up to run the mock inside of a JUnit test method. See stack trace below. I have set the build path so that it includes the soapui jar and has the SOAPUI_HOME/lib dir listed as an external class folder as well as setting all of the jars in the lib dir as external jars. Any ideas? java.lang.ExceptionInInitializerError at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:169) at org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.getMethod(SchemaTypeLoaderBase.java:73) at org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.<clinit>(SchemaTypeLoaderBase.java:66) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.xmlbeans.XmlBeans.getNoType(XmlBeans.java:856) at org.apache.xmlbeans.XmlBeans.<clinit>(XmlBeans.java:881) at com.eviware.soapui.config.SoapuiSettingsDocumentConfig$Factory.parse(Unknown Source) at com.eviware.soapui.DefaultSoapUICore.initSettings(DefaultSoapUICore.java:261) at com.eviware.soapui.DefaultSoapUICore.init(DefaultSoapUICore.java:146) at com.eviware.soapui.DefaultSoapUICore.<init>(DefaultSoapUICore.java:136) at com.eviware.soapui.tools.AbstractSoapUIRunner.createSoapUICore(AbstractSoapUIRunner.java:178) at com.eviware.soapui.tools.AbstractSoapUIRunner.run(AbstractSoapUIRunner.java:146) at com.bjm.MySoapUITester.test_SoapUIMock(MySOapUITester.java:124) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) at org.junit.runners.ParentRunner.run(ParentRunner.java:236) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197) Caused by: java.lang.NullPointerException at org.apache.xmlbeans.impl.store.Path.<clinit>(Path.java:65) ... 40 more1.8KViews0likes1CommentCreate good entry level documentation
I read through your REST documentation. Whoa - it's bad. If you don't make it easy for people to learn the basics, then it won't matter what technical features are available. Suggestions: 1. KISS: There are basically 4 REST functions paralleling the basic db functions, i.e. CRUD. Create 4 simple end-to-end tutorials that walk you through how to set each one of these up. Permute only the input/output format. For example, JSON is a very common exchange format. Make one of the 4 send JSON in the request and one return JSON in the response. Make another one send/exchange XML. Get the picture? 2. What happens when you cram a whole hamburger down someone's throat? They choke. Instead of trying to cram your whole feature set into one tutorial "thread", think of writing small, "chew-able" bites (tasks). 3. Developers don't necessarily make good tutorial/documentation writers. Occasionally you can find a developer who has writing skills, but that's more the exception than the rule. Good writers are who make good documentation creators, especially writers who have been formally trained in teaching. Get one - they will do far more for the market penetration of your software than the sales people. I don't want to talk to your sales people. As a developer, I want to deliver my code as quickly as possible. Either your software enables me to do that or it gets in my way. In this case, it wasted my time so I'm going to see if I can find another REST web service test framework that is a little more intuitive OR with better documentation. Otherwise, I'll waste the other 15 people on my project 's time.2.2KViews0likes1Comment