Contributions
rest (get) mock service configuration (dispatch error)
Hi All, being a long time user of soapui in soap context interfaces I am now involved with testing a HTTP Get Rest call. Since I noticed that soapui supports this as well I intend to use it for testing the gateway we have deployed here. The gateway is to function as a 100% passthrough of the request it receives. So I intend to use SOAPUI for both making REST call and capturing the forwarded (by the gateway) request with a Mock service. The request looks as follows: http://puhsap0010:8000/sap/geoe/arcgis/sync?sap-client=100&Command=U&ObjNr=IE000000000010927004&Category=B&ObjType=IE&TXNMSG=%7B%22attributes%22%3A%7B%22GEOCODE%22%3A%22107%22%2C%22KM_GEOCODE%22%3A%2212.74%22%2C%22AFKORTING%22%3A%22Ztmo%22%7D%7D&Direction=S&SubType=STATION My gateway receives this request (matched on the basis of the URI) and dispatches it further and ultimately makes a call to my mockservice (leaving all request parameters intact !) I have configured my mockservice for a GET method and a Resource path of : /sap/geoe/arcgis/sync In addition I created a response which is basically a HTTP 200 OK code. However when I run this I keep getting a [dispath error, missing response]. which the client sees as a <data contentType="null" contentLength="62"><![CDATA[Service response code: 404 Service response: Service status: ]]></data> and not the ok message I want to see. Judging by the error message two things might be incorrect 1. the resource path is not matched and therefore the dispatch error 2. or it matched but there is no response defined in some way. I currently suspect the first so the question is what the resource path should be in this type of situation ? I can't give it the full string because it will change with every call and I don't whether other mechanisms like e.g. wildcards are needed. If however you think the path is correct what could the reason that the response is not returned ? Thanks Peter2KViews0likes0CommentsRe: mockrequest schema checking
Hi Ole, thanks for the pointer. Followed all the instructions and got it to work. However I think it doesn't full bring what I am looking for. My impression is that it only checks for well-formed requests and not against schema definitions. So if I change e.g an opening tag and not the corresponding closing tag I get a validation error but if I change both tags the situation isn't captured. Could this have something to do with saxon ? licensing where some versions are schema-aware whilst others aren't ? If so can you indicate what needs to be done in the xmlbeans installation. Another thing I noticed is that pressing alt-v on the request message does seem to check against the schema. What I basically would like to achieve is having these kind of checks in my mock service once this request comes in. Thanks in advance Peter Geerts682Views0likes0Commentsmockrequest schema checking
Hi, possibly asked before but I am currently trying to have schema validation done on requests coming in on my mockservice. In my current setup addition of non compliant tags to my input message doesn't seem to bother the mock service invoked. What I would like to achieve is that the mock service complains about invalid dat in much the same way that the "real" service implementation will do in the next phase. Is there a way to have this verified ? Thanks in advance Peter Geerts1.8KViews0likes3CommentsRe: problem loading HL7 wsdl - outofmemory heap space
Hi Ole, yes I can do that. Will attach the rar file with all the definitions needend. When unpacked all references should work and you can try to load the wsdl. I am using 3.0.1 (but 2.5 behaves similar) and given 1024MB of memory Peter714Views0likes0Commentsproblem loading HL7 wsdl - outofmemory heap space
Hello, trying to get an wsdl definition loaded into SOAPUI that always results in an memory exception no matter how much space I provide. Log statements I see in the console are attached. Except for the few warning statements I have nothing to go on because everything seems to be loaded fine. Could the warnings be the cause of the problem and are they related to the file listed immediately above ? Both wsdl and all schema's validate in Oxygen 10.1 Thanks Peter Geerts1.6KViews0likes3Comments