Soapui mock dispatch error missing response

Mock-сервис SoapUI REST выдает ошибки при имитации для обработки динамических ответов в зависимости от значений запроса (но тот же метод работает для SOAP-mock)

Я пытался издеваться над следующей веб-службой REST с помощью soapUI

Обычно я использую такой отличный скрипт для оценки запроса и выдачи динамического ответа. (При использовании soapUI для имитации веб-сервисов SOAP)

К сожалению, когда я пытаюсь выполнить запрос к этой конечной точке фиктивной службы REST, он возвращает ошибку. Ошибка:

com.eviware.soapui.impl.wsdl.mock.DispatchException: Failed to dispatch using script; java.lang.NullPointerException: Cannot invoke method getRequestContent() on null object

Я понимаю, что в сообщении об ошибке говорится, что getRequestContent () вернул нулевое значение, и поэтому я получаю это исключение. Но то же самое работает с mock-сервисами SOAP, не возвращая нулевые значения или вызывая исключения. Благодарим за любые обходные пути для решения этой проблемы.

Я просто подумал, что mockRequest.getRequestContent () возвращает null для всех запросов POST, PUT, DELETE, отправленных веб-службам REST, имитируемым с помощью soapUI (версия 5.2.1)

Поскольку приведенный выше (RequestContent) возвращает значение null, пользовательский интерфейс мыла не может оценить значение следующего тега.

SoapUIOfficial References for this bug in soapUI(version 5.2.1):

Я только что нашел обходной путь, чтобы преодолеть вышеупомянутую ошибку в soapUI (версия 5.2.1).

К этому моменту мне стало ясно, что я могу использовать скрипт mockRequest.getRequest (). GetReader (). ReadLine () для чтения одной строки в теле запроса. (хотя mockRequest.getRequestContent () вернул нулевой объект)

Я бы просто получил доступ к телу запроса, используя следующий отличный скрипт.

Согласно приведенному выше сценарию, он должен будет прочитать тело запроса построчно, а затем объединить все строки, чтобы получить все тело запроса .

Поскольку тело запроса больше не является нулевым, следующий скрипт может оценить значение внутри ссылочного тега.

в конце концов я смог издеваться над своим макетным сервисом REST с динамическими ответами в соответствии со следующими условиями.

Надеюсь, вы сможете сэкономить много времени, следуя этому методу.

Источник

ole lensmar’s blog

Monday, May 27, 2013

SoapUI + Swagger = true!

Since I published the original version of the soapui-swagger-plugin in late 2012, Swagger has continued to gain traction within the API community. For those of you not familiar with Swagger, it’s a metadata format for describing the ins and outs of a REST API — much like WSDL is for SOAP APIs — have a look at the Swagger website to learn more.

The initial version of the plugin allowed you to import Swagger definitions into SoapUI — making it extremely easy to send ad-hoc requests, create functional tests, load tests and API monitors for the Swagger-described API (and all for free!). When discussing the plugin with some users at APIStrat earlier this year, they requested the possibility to be able to export Swagger definitions as well, i.e. if you have a REST API defined in SoapUI — they wanted to be able to generate a corresponding Swagger definition that they (for example) could use with swagger-ui to provide your customers an online tool for trying out your API.

Obviously I couldn’t resist the challenge, and although its taken me some time I’m happy to finally announce version 0.2 of the plugin that does exactly that; exports Swagger definitions for any REST API defined in SoapUI — which has some cool usage scenarios. Let’s dive in.

REST APIs in SoapUI

Despite its contextually unfortunate name — SoapUI has had good support for testing REST APIs since 2008 (!). REST support was initially modeled around the WADL specification (an initial attempt at providing metadata for REST APIs) — fortunately the object model in Swagger plays pretty well with WADL, which makes the Swagger import/export feature in the plugin play seamlessly with SoapUIs REST support.

Exporting Swagger Definitions

Exporting Swagger definitions using the plugin is straightforward; make sure you have at least one REST API defined in your SoapUI project and right-click the project node in the SoapUI navigator; the popup menu now has an «Export Swagger» menu option:

Select it to bring up the following dialog:

The settings are as follows:

• APIs : select which REST APIs in your project that you want to include in the generated Swagger definition
• Target Folder : where to generate the files
• API Version : the value for the api-version property in the generated definitions
• Base Path: the base path that the generated resource listing will be hosted on. This is important to get right as API declarations are resolved relative to this (see example below)
• Format : which format to use; Swagger technically supports both json and xml, although I would guess 99% of its users are using json at this time 🙂

Press the OK button when you’ve set the options as desired; SoapUI will work a little and prompt you with the path of the generated Swagger resource listing. This is ready to go; feed it into any other tool that supports Swagger — for example you can use swagger-ui to provide a nice online UI for exploring the described API (see example below).

Usage Scenarios

Although the primary usage scenario may be the one described further down in this post — generating Swagger definitions for hosting them with swagger-ui — you could of course use the export feature of the plugin for things like:

• WADL to Swagger conversion; if you have API definitions in WADL format you can simply import them into SoapUI (using the regular Add WADL functionality) and then export them as Swagger definitions with this Plugin
• Swagger-creation; if you need a visual tool to build Swagger definitions «from scratch» you can use SoapUI to define your REST API which you can then export.

Hosting Swagger definitions with SoapUI

One thing you might want to do is provide your API users with a nice browser-based UI for trying out your API — which is precisely what the swagger-ui project is for (also from the Swagger folks). You can download swagger-ui from GitHub and just open it from your local file system in your browser — which will start you with something like:

(by default it displays the sample petstore Swagger definition)

Now how do you get swagger-ui to read the resource-listing generated by SoapUI? Unfortunately swagger-ui doesn’t support file-based URLs so we need to do a bit of trickery with SoapUI to expose our Swagger for swagger-ui; the MockService functionality in SoapUI can be used as a miniature web-server, which is just what we need here (if you have a local web server running you can of course use that instead).

Start by creating a MockService in your SoapUI project via the Project menus «New MockService» option. Once created — double-click it to open the MockService window and select the «Options» button — which will bring up the following dialog:

Set the docroot to point at the folder where you generated the Swagger definition, configure the port as desired (so it doesn’t collide with anything else you might be hosting on your machine), press OK and start the MockService with the «Run» button in the top-left corner of the MockService window. You now have a mini webserver running, ready to serve any documents you have in the specified docroot folder, but before we can use swagger-ui with it we need to make sure the MockService adds some HTTP Headers that swagger-ui expects. Select the «OnRequest Script» tab in the MockService window and enter the following:

mockRequest.httpResponse.addHeader( «Access-Control-Allow-Origin», «*» )
mockRequest.httpResponse.addHeader( «Access-Control-Allow-Methods», «GET, POST, DELETE, PUT» )
mockRequest.httpResponse.addHeader( «Access-Control-Allow-Headers», «Content-Type, api_key, Authorization» )

In SoapUI, this looks as follows;

Let’s go back to the dialog for Exporting Swagger definitions and configure it accordingly:

Please note that Base Path configuration above matches the local ip that the MockService is running on (so the path can be resolved) and the Target Folder is the same as the docroot for the MockService configured above. Once exported we’re all set; open a web-browser and enter «http://127.0.0.1:8181/api-docs.json» (change the port accordingly) — which should bring up the Swagger resource listing we generated above;

Now back to swagger-ui; paste the same endpoint in the URL field and press the «Explore»; swagger-ui will work a bit and presto, you should get something like the following;

Awesome — we’ve created Swagger definitions for some of the Google Maps APIs and can now do some simple API invocation from within swagger-ui!

Changes to the Import Swagger feature

The «Import Swagger» feature has been improved a little since last; the dialog invoked by the corresponding menu item now looks as follows:

Here you can now specify to import Swagger API Declarations directly (instead of always having to provide a Resource Listing) — which can come in handy for some of the API-mgmt platforms out there that provide API Declarations directly (APIHub for example).

A bonus under the hood: swagger4j

Version 0.2 of this plugin needed a more robust way to read and write Swagger definitions than the groovy scripts that were used in version 0.1 to just read them. I’ve separated this into a separate java library — swagger4j — which has no dependencies on SoapUI whatsoever and can as such used within any Java program that needs to read or write Swagger definitions. It’s open-source (Apache licensed) and available over at GitHub — check it out, and don’t hesitate to give me feedback so I can improve that as well.

Installation

Installing the plugin is straight forward; download it from sourceforge or build it yourself with maven (it’s on GitHub). The download from sourceforge contains the required dependencies — all you have to do is unzip it into your SoapUI/bin folder.If you build it manually you will have to add these dependencies yourself to the SoapUI/bin/ext folder:

Next Steps

So what’s next? You tell me! Please get in touch if you want to see any specific fixes, improvements, etc — I’d love to hear from you.

Thanks, It helps a lot.

It will be good if we have maven plugin for WADL to Swagger json.

Cool idea — please add it to the issue tracker at GitHub: https://github.com/olensmar/soapui-swagger-plugin

Well — I downloaded it and unzipped into Soapuibin directory and now how do I use it to automate my SWAGGER REST API, plus how I can get it to work with request input using this as an example:

<
«name»:»DONNAS Test»,
«description»:»DONNAS Test»
>

It will not work — I exported REST API using SWAGGER and Imported it back in. I tried to execute the test, but to no avail I get HTTP 404. Do you have any examples of POST, PUT, DELETE, etc using SOAPUI PRO?

hmm. is the plugin perhaps extracting the wrong URL endpoint from the swagger definition? Could you attach the swagger def here and let me know how the generated request differs from one that works?!

thanks in advance!

Hi!
Is it possible to get a body included in the swagger def? Both from the request body of POST/PATCH/PUT, and from response body in all methods? (Given that the bodies are json)

Hi
I am trying to export rest rervice definition to swagger format and get the following error:
Thu Oct 31 16:46:49 CET 2013:ERROR:java.lang.NoClassDefFoundError: com/smartbear/swagger4j/Constants$Format
java.lang.NoClassDefFoundError: com/smartbear/swagger4j/Constants$Format

thanks is advance.

hmm. do you have the swagger4j jar file in the soapui/bin/ext folder?

No i don’t!!
Where can i download it?

Hi Ole,
after copying javax.json-1.0-b06.jar and swagger jar it works correctly.

Great! Please don’t hesitate to comment ideas for improvements, etc!

# Installation on OS X

I am using the soapui-swagger-plugin with the OS X version of soapui. I copied the content of the zip file into /Applications/SoapUI-4.6.3.app/Contents/java/app/bin and this seems to work, although I could not find documentation about this anywhere.

When importing from swagger spec into soapui, can I only do this from a json file, or also from a URL that points to a swagger spec? I only got it to work from file. This probably has to do with the following issue though.

My API uses HTTP Basic Auth, so even to retrieve the swagger spec, one needs to authenticate. URL in my case is
http://localhost:3000/api/v1/swagger_doc.json

I tried to add username/password in the URL directly but that didn’t work.

I get errors like «java.io.IOException: Server returned HTTP response code: 401 for URL: http://localhost:3000/api/v1/abc»

sorry for the late response — please add a feature request for HTTP authentication support at https://github.com/olensmar/soapui-swagger-plugin/issues and I’ll try to get this fixed.

Sebastian — are you using soap ui pro? I can not sem to get the swagger menu items

Hi. I used Spring ‘swagger-springmvc’ to generate the Swagger URLs from a Spring project. These files work fine with ‘swagger-ui’. However, when I try to import into SoapUI (Import Swagger) then I get a ClassCastException:

Sun Jan 12 21:34:57 GMT 2014:ERROR:java.lang.ClassCastException: javax.json.JsonValue$1 cannot be cast to javax.json.JsonArray
java.lang.ClassCastException: javax.json.JsonValue$1 cannot be cast to javax.json.JsonArray
at org.glassfish.json.JsonObjectBuilderImpl$JsonObjectImpl.getJsonArray(JsonObjectBuilderImpl.java:161)
at com.smartbear.swagger4j.impl.SwaggerParser$SwaggerJsonParser.getChildren(SwaggerParser.java:211)
at com.smartbear.swagger4j.impl.SwaggerReaderImpl.readOperation(SwaggerReaderImpl.java:251)
at com.smartbear.swagger4j.impl.SwaggerReaderImpl.readApiDeclaration(SwaggerReaderImpl.java:224)
at com.smartbear.swagger4j.impl.SwaggerReaderImpl.readApiDeclaration(SwaggerReaderImpl.java:176)
at com.smartbear.swagger4j.SwaggerReader$readApiDeclaration.call(Unknown Source)

hmm. can you send me the Swagger file so I can try importing it!? (olensmar a t gmail.com)

SoapUI doesn’t seem to manage some Swagger attributes like models, authorizations, type or items (to refer to the models and show response data model in swagger), etc.

Are these some extra info to add by hand once Swagger description file generated ?

you’re right — unfortunately SoapUI doesn’t support models/types and JSON Schemas at this point — the authorizations metadata will be supported by an updated version of the plugin once SoapUI 5.0 is released.

Doesn’t work with SoapUI 5.0 on OSX.

Yes can not get it work on Mac using SoapUI 5.0 — does this only work on SoapUI pro or only

Hi,
I’m having some troubles generating the swagger json file from inside soapui 5.0. All the jars are in the right folder, when I click the ok button of the generation dialog I obtain the following trace in the error.log file. Any advice? Downgrade soapui ? Thanks in advance.
Rob

Fri May 02 12:45:55 CEST 2014:ERROR:java.lang.NoClassDefFoundError: com.eviware.soapui.impl.rest.RestRequestInterface$RequestMethod
java.lang.NoClassDefFoundError: com.eviware.soapui.impl.rest.RestRequestInterface$RequestMethod
at com.smartbear.restplugin.SwaggerExporter$_generateResourceListing_closure2_closure3_closure4.class$(SwaggerExporter.groovy)
at com.smartbear.restplugin.SwaggerExporter$_generateResourceListing_closure2_closure3_closure4.$get$$class$com$eviware$soapui$impl$rest$RestRequestInterface$RequestMethod(SwaggerExporter.groovy)
at com.smartbear.restplugin.SwaggerExporter$_generateResourceListing_closure2_closure3_closure4.doCall(SwaggerExporter.groovy:107)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90)
at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:233)
at org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:272)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:909)
at groovy.lang.Closure.call(Closure.java:411)
at groovy.lang.Closure.call(Closure.java:427)
at org.codehaus.groovy.runtime.DefaultGroovyMethods.each(DefaultGroovyMethods.java:1325)
at org.codehaus.groovy.runtime.DefaultGroovyMethods.each(DefaultGroovyMethods.java:1297)
at org.codehaus.groovy.runtime.dgm$148.invoke(Unknown Source)
at org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite$PojoMetaMethodSiteNoUnwrapNoCoerce.invoke(PojoMetaMethodSite.java:271)
at org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite.call(PojoMetaMethodSite.java:53)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:116)
at com.smartbear.restplugin.SwaggerExporter$_generateResourceListing_closure2_closure3.doCall(SwaggerExporter.groovy:85)
.

Guys — sorry to keep you waiting on this — I’ll publish a fixed version over the weekend!

Hi Ole,
I am just starting to use SoapUI 5.0, I have added your plugin.

My actual goal is to import a definition(s) from a site that uses an Access-Token in the header even for the definitions. It also uses models and items . as mentioned above. I can create a resource by hand and first get the access token, then insert it into a header and I will get back the swagger json for the resources, but I don’t see how to do this all and get it into SoapUI as forms (pardon my terminology, im new to swagger and SoapUI REST, though I have use SoapUI Soap)

to try and debug i then tried the petstore project, but I am getting errors here also:
Generic project and Add Swagger Definition, either type I get file not found for the http://petstore.swagger.wordnik.com/api/api-docs.json.
I get a file not found error for this. I got the link from your 2012/12 tutorial. I then tried without the .json extension. This gives me
java.lang.ClassCastException org.glassfish.json.JsonObjectBuilderImpl$JsonObjectImpl cannont be cast to javax.json.JsonString

I then put the Url http://petstore.swagger.wordnik.com/api/api-docs (no .json) into firefox and got back would appears to be the valid swagger json definition. it indicates apiVersion 1.0.0 and swaggerVersion 1.2

i see you are planning on making a fix this weekend, so if there is something you would like me to try let me know

I’ve updated the swagger4j library that was causing these issues (for me at least) — please grab the latest version from https://sourceforge.net/projects/swagger4j/files/1.0-beta3/ and replace the beta2 version of swagger4j in your SoapUI/bin/ext folder with it.

Let me know if that helps — thanks!

Error after copying beta3 jar to SoapUI/bin/ext. Please help.

Directory of C:viewsinstallationSmartBearSoapUI-5.0.0binext
..
05/16/2013 12:04 AM 78,456 javax.json-1.0-b06.jar
04/09/2014 10:44 AM 150 readme.txt
05/05/2014 03:47 PM 73,857 swagger4j-1.0-beta3.jar

Mon May 05 15:52:44 EDT 2014:ERROR:java.lang.NoClassDefFoundError: com.eviware.soapui.impl.rest.RestRequestInterface$RequestMethod
java.lang.NoClassDefFoundError: com.eviware.soapui.impl.rest.RestRequestInterface$RequestMethod
at com.smartbear.restplugin.SwaggerExporter$_generateResourceListing_closure2_closure3_closure4.class$(SwaggerExporter.groovy)
at com.smartbear.restplugin.SwaggerExporter$_generateResourceListing_closure2_closure3_closure4.$get$$class$com$eviware$soapui$impl$rest$RestRequestInterface$RequestMethod(SwaggerExporter.groovy)
at com.smartbear.restplugin.SwaggerExporter$_generateResourceListing_closure2_closure3_closure4.doCall(SwaggerExporter.groovy:107)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)

Darn — I’ll update the RAML plugin instead. gimme a day or two — sorry to keep you waiting!

what is RAML plugin ? i am not sure about what you mean.
in around end of 2013, i had pre soap 5.0 installed and i recall was able to generate swagger output from my imported wadl restapi. worked perfect then.

now with soap ui 5.0 trying to do the same, fails with the error i reported above even after using the beta-3 jar.
Let me know if you need some debug output or anything else.
thanks.

Источник

I want to mock a Webservice for development environment.
I have SOAPUI version 5.2.1 and the following WSDL:

<wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" 
xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" 
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" 
xmlns:s="http://www.w3.org/2001/XMLSchema" 
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" 
xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" 
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" 
xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" 
xmlns:tns="http://server.com/SSO" 
targetNamespace="http://server.com/SSO">
    <wsdl:documentation>Web service</wsdl:documentation>
    <wsdl:types>
        <s:schema elementFormDefault="qualified" targetNamespace="http://server.com/SSO">
            <s:element name="GetProfile2">
                <s:complexType>
                    <s:sequence>
                        <s:element maxOccurs="1" minOccurs="0" name="Token" nillable="true" type="s:string"/>
                        <s:element maxOccurs="1" minOccurs="0" name="SiteName" nillable="true" type="s:string"/>
                        <s:element maxOccurs="1" minOccurs="0" name="TimeStamp" nillable="true" type="s:string"/>
                        <s:element maxOccurs="1" minOccurs="0" name="EncodedPwd" nillable="true" type="s:string"/>
                        <s:element maxOccurs="1" minOccurs="0" name="EncodedType" nillable="true" type="s:string"/>
                        <s:element maxOccurs="1" minOccurs="0" name="Filter" nillable="true" type="s:string"/>
                    </s:sequence>
                </s:complexType>
            </s:element>
            <s:element name="GetProfile2Response">
                <s:complexType>
                    <s:sequence>
                        <s:element maxOccurs="1" minOccurs="0" name="GetProfile2Result" type="s:string"/>
                    </s:sequence>
                </s:complexType>
            </s:element>
            <s:element name="GetCache">
                <s:complexType/>
            </s:element>
            <s:element name="GetCacheResponse">
                <s:complexType>
                    <s:sequence>
                        <s:element maxOccurs="1" minOccurs="0" name="GetCacheResult" type="s:string"/>
                    </s:sequence>
                </s:complexType>
            </s:element>
            <s:element name="string" nillable="true" type="s:string"/>
        </s:schema>
    </wsdl:types>
    <wsdl:message name="GetProfile2SoapOut">
        <wsdl:part element="tns:GetProfile2Response" name="parameters">
        </wsdl:part>
    </wsdl:message>  
    <wsdl:message name="GetProfile2SoapIn">
        <wsdl:part element="tns:GetProfile2" name="parameters">
        </wsdl:part>
    </wsdl:message>
    <wsdl:portType name="ServiceSoap">
        <wsdl:operation name="GetProfile2">
            <wsdl:documentation>Returns a user</wsdl:documentation>
            <wsdl:input message="tns:GetProfile2SoapIn">
            </wsdl:input>
            <wsdl:output message="tns:GetProfile2SoapOut">
            </wsdl:output>
        </wsdl:operation>
        <wsdl:operation name="GetCache">
            <wsdl:documentation>Returns the cached abilitations.</wsdl:documentation>
            <wsdl:input message="tns:GetCacheSoapIn">
            </wsdl:input>
            <wsdl:output message="tns:GetCacheSoapOut">
            </wsdl:output>
        </wsdl:operation>
    </wsdl:portType>
    <wsdl:binding name="ServiceSoap" type="tns:ServiceSoap">
        <soap:binding transport="http://schemas.xmlsoap.org/soap/http"/>
        <wsdl:operation name="GetProfile2">
            <soap:operation soapAction="http://server.com/SSO/GetProfile2" style="document"/>
            <wsdl:input>
                <soap:body use="literal"/>
            </wsdl:input>
            <wsdl:output>
                <soap:body use="literal"/>
            </wsdl:output>
        </wsdl:operation>
        <wsdl:operation name="GetCache">
            <soap:operation soapAction="http://server.com/SSO/GetCache" style="document"/>
            <wsdl:input>
                <soap:body use="literal"/>
            </wsdl:input>
            <wsdl:output>
                <soap:body use="literal"/>
            </wsdl:output>
        </wsdl:operation>
    </wsdl:binding> 
    <wsdl:service name="Service">
        <wsdl:documentation>Web service</wsdl:documentation>
        <wsdl:port binding="tns:ServiceSoap" name="ServiceSoap">
            <soap:address location="http://server.com:7001/services/Service.ServiceSoap/"/>
        </wsdl:port>   
    </wsdl:service>
</wsdl:definitions>

I’ve created in SOAPUI a new soap project, with mock service, I’ve set the host and the port of the Weblogic server 12c where I have to install the war.

In SOAPUI preferences I have unchecked Logs wire content of all…», in MockService Properties I have set «Require SAOP Action» to false, and I’ve export as WAR the project and install into Weblogic 12c.

Ok, the problem is that, the first call to the webservice is ok, and I get the expected response.

From the second call I get the following error:

com.eviware.soapui.impl.wsdl.mock.DispatchException: Missing operation for soapAction [http://server.com/SSO/GetProfile2] and body element [{http://server.com/SSO}GetProfile2] with SOAP Version [SOAP 1.1]
at com.eviware.soapui.impl.wsdl.support.soap.SoapUtils.findOperationForRequest(SoapUtils.java:330)
at com.eviware.soapui.impl.wsdl.mock.WsdlMockDispatcher.dispatchPostRequest(WsdlMockDispatcher.java:191)
at com.eviware.soapui.impl.wsdl.mock.WsdlMockDispatcher.dispatchRequest(WsdlMockDispatcher.java:113)
at com.eviware.soapui.impl.wsdl.mock.WsdlMockRunner.dispatchRequest(WsdlMockRunner.java:142)
at com.eviware.soapui.mockaswar.MockAsWarServlet$MockServletSoapUICore.dispatchRequest(MockAsWarServlet.java:247)
at com.eviware.soapui.mockaswar.MockAsWarServlet.service(MockAsWarServlet.java:182)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:286)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:260)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:137)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:350)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:247)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3650)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3620)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:326)
at weblogic.security.service.SecurityManager.runAsForUserCode(SecurityManager.java:196)
at weblogic.servlet.provider.WlsSecurityProvider.runAsForUserCode(WlsSecurityProvider.java:203)
at weblogic.servlet.provider.WlsSubjectHandle.run(WlsSubjectHandle.java:71)
at weblogic.servlet.internal.WebAppServletContext.doSecuredExecute(WebAppServletContext.java:2423)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2280)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2258)
at weblogic.servlet.internal.ServletRequestImpl.runInternal(ServletRequestImpl.java:1626)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1586)
at weblogic.servlet.provider.ContainerSupportProviderImpl$WlsRequestExecutor.run(ContainerSupportProviderImpl.java:270)
at weblogic.invocation.ComponentInvocationContextManager._runAs(ComponentInvocationContextManager.java:348)
at weblogic.invocation.ComponentInvocationContextManager.runAs(ComponentInvocationContextManager.java:333)
at weblogic.work.LivePartitionUtility.doRunWorkUnderContext(LivePartitionUtility.java:54)
at weblogic.work.PartitionUtility.runWorkUnderContext(PartitionUtility.java:41)
at weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkManagerImpl.java:617)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:397)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:346)

If i remove the message tags from wsdl everything is ok. Help me Please!!!

Soap UI for simulating a Rest API??? Well, it wasn’t even the last thing that came to my mind when one of my former colleagues asked me if I could quickly create a mock up for a REST API for the application he was testing because the API was down at the moment.

By the way, here’s why you should mock a REST API,

• It enables you to stay productive while the API is being implemented.
• Mocks could be used for testing and developing the front end even when the back end is not available.

I thought it could be done in no time with Postman. I had quite a bit of experience with Postman, testing REST APIs, but soon realized it wasn’t quite as straightforward as I thought.
Then I had a quick look at some other tools available for the purpose, some were way too complicated to be bothered for such a temporary quick fix and others were mostly hosted online. Couldn’t find much luck with any thing so far for my purpose and that’s when a simple google search directed me to soap ui. I already had it installed and am quite good at it, testing and mocking soap web services, so I decided to give it a go. To my surprise, it’s not only easy and fast but also quite powerful in simulating REST APIs.

Following are some of the things I tried and step by step instructions on how to.

• How to create a simple mock.
• How to mock resource paths with variables.
• How to set up multiple mock responses depending on request.

Install Soap UI if you don’t have already, and following are the steps after that.

How to create a simple mock.

1. Create a new REST project in Soap UI following the screens below.

Click the REST button on the tool bar (circled in red).

Give an appropriate URL. I have provided http://localhost:8080/test. You can change these later.

Following is the new project that was just created (REST Project 2)

2. Create a Mock for the REST project

Right click on the project and select New REST MockService from the menu.

Give an appropriate name for the MockService

Right click on the Mock Service and select Add new mock action from the menu.

Select the HTTP method and give the resource path, it can be anything. I have selected GET method and my resource path is test.

3. Add a mock response

Right click on the action and select New MockResponse from the menu.

Give an appropriate name to the mock response.

Select the response content type (i.e. xml, json, text, etc…) and type in the mock response

4. Start the mock service

Right click on the MockService and select Show REST MockService Editor.

Click the green play button on the MockService Editor (circled in red), and the Mock service will start.

5. Test it out!

Send a request using the REST Project by clicking the green play button on the request.

The mock service can also be called using a browser

Mocking for resource path with variables.

Most REST URLs contain variables in the resource path, like https://example.com/users/679822 which are basically ids or names which change depending on the request. If you are wondering how to handle these, the good news is, it is already taken care of. If we just use up to users in the resource path of the mock, whatever comes after it in the request url doesn’t really matter. This behavior is demonstrated in REST Project 3 (You can grab these project files by clicking here, and import in to Soap UI)

How to set up multiple mock responses

Want to work with multiple responses for a single path? There are two options available in Soap UI.

1. Sequence

This is easy, create as many responses as you like for the mock action. The default dispatch method is sequence.

Open up the mock action editor by double clicking on the mock action or by right click on the mock action and selecting Show Mock Action Editor. Add as many responses as you want.

The HTTP status code can also be set to preferred value in the responses. In the example below (REST Project 4) I have created 3 mock responses and one of them is an error response which returns http status 500.

See it in action

2. Script

When you want different responses depending on the request (request path or a value in the request) script option can be used.

1. Create multiple responses.
2. Select the script option from the dispatch drop-down for the mock action.
3. Then provide the script, following is the script I’ve used.

//Following script grabs the number in the request url and appends it to the name of the response.

def requestPath = mockRequest.getPath()
log.info "Path: "+ requestPath

def id = requestPath.tokenize('/')[-1] //the id of the user comes last in the request url (eg: http://localhost:8080/user/1)

return "user"+id //this will return the response with the name 'user{id}' eg: user1

1. Set a default response in case no matches found for the incoming request.

See it in action

That’s all I have come across so far with Mocking REST APIs using Soap UI.

Which tools have you used for simulating REST APIs? Any suggestions?