Hi,We have a large number of optional elements in our Service requests. One of the issues I am coming accross regularly is a number of them cannot be passed as empty tags due to the type declaration. We have build a framework driven from excel datasheets but we don't want to have to build large numbers of template requests based on different business rules. Is there a way of only stripping the empty optional elements before a request is sent to the service? Does SoapUI Pro have this functionality or do I need to script something to handle it?One way I thought would be to have a listener that calls a script to remove any empty elements from the request by default unless specified in the datasheet. Is this possible? I can't find any examples of using a listener on a particular test step or any examples of where I would start.ThanksDarren

Hi Darren,before we dig into listeners; have you tried the "Remove Empty Content" option on the Request level (bottom left properties..)?regards!/Oleeviware.com

Hi Ole,Ah yes I just come across the feature, this morning while debugging a listener to do the same thing :-( Hopefully that should fix most of the issues.There may still be a time where I need to pass an empty element in the Request. The idea is to have predefined global Keyword that maps to a function, for example if the listener sees the value $#BLANK#$ in a request it will strip the value from the tags. Is there a way the listener can read a request after the "Remove Empty Content" has occured but before the Request is sent to the Service? Another quick question too, is there a quick way of checking a response is a soap fault in a script assertion? for exampleif (response == soapfault){ fail assertion}pass assertion CheersDarren

Hi Darren, here comes the code for a DemoRequestFilter that removes all elements containing "--remove--" from the outgoing request:package soapui.demo import com.eviware.soapui.SoapUI import com.eviware.soapui.impl.wsdl.submit.transports.http.BaseHttpRequestTransport import com.eviware.soapui.impl.wsdl.submit.RequestFilterimport com.eviware.soapui.impl.wsdl.WsdlRequest import com.eviware.soapui.model.iface.Responseimport com.eviware.soapui.model.iface.SubmitContextpublic class DemoRequestFilter implements RequestFilter{ public void afterRequest( SubmitContext context, Response response ) {} public void filterRequest( SubmitContext context, WsdlRequest wsdlRequest ) { String content = (String) context.getProperty( BaseHttpRequestTransport.REQUEST_CONTENT ) if( content == null ) { System.err.println( "Missing request content in context, skipping demofilter" ) } else { System.out.println( "running demofilter" ) content = content.replaceAll( "<(.+)>--remove--</(\\1)>", "" ) context.setProperty( BaseHttpRequestTransport.REQUEST_CONTENT, content ) } } }Put this in the soapuipro\bin\scripts folder and add a demo-listeners.xml file in the soapuipro\bin\listeners folder containing:<?xml version="1.0" encoding="UTF-8"?><tns:soapui-listeners xmlns:tns="http://eviware.com/soapui/config"> <tns:listener id="DemoListener" listenerClass="soapui.demo.DemoListener" listenerInterface="com.eviware.soapui.model.testsuite.TestRunListener" /> </tns:soapui-listeners>The listener uses the standard regex-based String.replaceAll to remove these tags, you should be able to tweak it as required. Regarding the SOAP-Fault, you could try using the same code as the NotSoapFaultAssertion:def responseContent = messageExchange.responseContentdef soapVersion = messageExchange.operation.getInterface().soapVersionassert !com.eviware.soapui.impl.wsdl.support.soap.SoapUtils.isSoapFault( responseContent, soapVersion )ok.. hope I got all that right :-)regards!/Oleeviware.com

Good Stuff Ole.That's exactly what I wanted, couldn't figure out exactly where I need to apply the filter before it gets sent to the service. This will allow us to do quite a bit of manipulation of the requests based on predefined "keywords” supplied in the datasheets which map to specific functions.Thanks

Hi Ole, Been trying to get this to work but I think there is something wrong with the entry in the demo-listeners.xml file. Any chance you could confirm if this is correct?Darren

Listeners - Modifying Requests before posting to a Service

16 Replies

cdunne
Contributor
16 years ago
Hi Ole,

I had an older version of SoapUI Pro on the machine which I removed, plus I removed all my scripts. I now get teh following error at startup.

09:05:36,752 INFO [DefaultSoapUICore] Adding listeners from [C:\Program Files\e
viware\soapUI-Pro-2.0.3\bin\listeners\demo-listeners.xml]
Error initializing Listener: java.lang.RuntimeException: Listener class: soapui.
demo.DemoListener must implement interface: com.eviware.soapui.model.testsuite.T
estRunListener

Makes a bit more sense now.
Cheers

Darren
omatzura
Super Contributor
16 years ago
Hi Darren,

duh.. the fault is mine.. the config should be

listenerInterface="com.eviware.soapui.impl.wsdl.submit.RequestFilter" />

works better?

regards,

/Ole
eviware.com
cdunne
Contributor
16 years ago
Hi Ole,

Thanks for that, it now appears to be running the filter. Any way of checking if the correct request is being sent?

I've tried adding

SoapUI.log.info("request sent: "+context.getProperty( BaseHttpRequestTransport.REQUEST_CONTENT ))

after the new message is set but that prints the request unmodified. Is this correct, if so then I must have a problem with the filter?

Cheers

Darren
omatzura
Super Contributor
16 years ago
Hi Darren,

hmm again :-) In what does this not work? Gives an error? Shows the wrong request? etc..

regards!

/Ole
eviware.com
cdunne
Contributor
16 years ago
Hi Ole,

Oh yeah sorry if I add --empty-- in an element I would expect that element to be stripped out of the request. For example,

MDUserDescTyMeteor
MDAppDescTyWeb
MDAppIDTyMDS

--empty--

--empty--

I would expect the following request to be sent,

MDUserDescTyMeteor
MDAppDescTyWeb
MDAppIDTyMDS

If I add that extra line in the filter, after the setProperty call,
SoapUI.log.info("request sent: "+context.getProperty( BaseHttpRequestTransport.REQUEST_CONTENT ))

I would expect the updated request to be printed to the log?

Cheers

Darren
omatzura
Super Contributor
16 years ago
Hi Darren,

unless you've changed the code, it should be "--remove--", not "--empty--". Is that it?

regards!

/Ole
eviware.com

Forum Discussion

Listeners - Modifying Requests before posting to a Service

16 Replies

Related Content

Listener events not getting registed when running through maven

Listeners

Request Not Modified

Modify response with request data

How to modify request endpoint property

Recent Discussions

Executing test case loop multiple times

Error connecting to Postgress DB in ReadyAPI 3.52.0

GroovyScript - Extract specific number of attribute values from variable content response

How to create Identical GET request with different parameters in same project

Path parameter always gives default response