I can't find any mention of testing stateful services.  I make a project, get the wsdl, try to connect/login request, which works, but all subsequent requests get 'no connection'.  Had to write the services statefully, would be nice to use this to test them.

The server returns a set-cookie header with the JSESSIONID.
The client is supposed to return the JSESSIONID in a http header,
which I have not seen either with soapUI.  It would be nice if that worked (cookie handler functionality).

Hi,

I found this older topic, dealing with a similar issue to mine. I'm using SoapUI 2.0 Beta and I need to test a stateful service. As Ole suggests above, I looked in the Test Case Options dialog.  I checked 'Maintain HTTP Session' but that doesn't seem to copy cookies received in one response to the next request.

I too have a Set-Cookie: JSESSIONID=xxx in my first response, and if I copy this value to an HTTP header in the second request manually the session behaviour works fine. Is there another way of having SoapUI copy these cookie values automatically?

Thanks John

Hi,

I am also in a similar situation where in i have to test stateful services.
I have also enabled the option in the Test suite to maintain Http session.
It all works fine when i manually copy and paste the Set Cookie =XXX id into the request header of another request after login.

The sequence of steps that i have is
1 login :request step
2 set session : groovy script
3 do XYZ : request step

if i use the script as given in the example as in step2 (set session : groovy script) like

def state = context.getProperty( com.eviware.soapui.model.testsuite.TestRunContext.HTTP_STATE_PROPERTY )

i am getting the value of the state as null.

I am unable to proceed further because of this.Please let me know if i am wrong any where.Kindly help me fix this groovy script so that i can capture the session id of login method and add it in the subsequent requests in the groovy script.

Appreciate any help in this regard.

Thanks,
Lakshmi