How does stateful setting on service package for rest services behave
As per rest specification, they mention that Rest is stateless and client session/context is not maintained at server side. Each transaction works as atomic transaction.
Coming to Pega, if we enable stateful setting on the service package for the rest services how does it behave?
Accepted Solution
Pegasystems Inc.
IN
Yeah, by default, REST Services are stateless. Upon enabling stateful processing mode in service package, successive service requests will share the state provided PegaRULEs cookie is exchanged.
For more details see : https://pdn.pega.com/comparing-stateful-and-stateless-services/comparing-stateful-and-stateless-services
Cognizant Technology Solutions
US
@Sekhci
How do we ensure that pega cookie is exchanged as part of rest trasaction. I guess by default pega cookies will be sent in the response of the first transaction and there after responsibility will be on the client to maintains this cookie and include it in the subsequent requests. Using this cookie pega will identify any existing sessions and will process the subsequent request in the context of the primary/first request. Is my understanding is correct?
Also does tools like soap UI provides a way to test stateful rest services?