Here, first we set context of a state using a dynamic fetched value from request1- "context": "{{xPath request.body '//creationId/text()'}}", Later, we try to access that context, which we actually don't know as it had been fetched from XML request's one of the field. {{state context='dynamicValue??*'*property='id'}} I believe we must send the dynamic value to the context so that each request(ultimately through context) has a uniqueness to be identified and later to be accessed correctly

in case you don't want the first run to interfere with the next, you can delete it in your

details

call:

"serveEventListeners": [
    {
      "name": "deleteState",
      "parameters": {
        "context": "sc nam"
      }
    }
  ]

@Dirk Bolte, but see my req1 has a unique value which I can provide as context, later matching same context with req2's URL or other things BUT my req2 only has a URL which is all static does't have any dynamic value. req2 returns a a body where I'll put state value as needed now here question is how will we make req2 in context w.r.t. each req1 object

Here's the drawback while working with a static context, I had already tried-

Here's the drawback while working with a static context, I had already tried. you can correct me here if anything- as multiple POST requests are made, GET would only respond for latest POST request

if there's no identification within the request, there needs to be something different

a stack, an order, ...

that's what I know

similar to stack somehow

we work either JSONs

I found it, let me check

is there any persistence or something

@Dirk Bolte, PFB { "mappings": [ { "priority": 2, "request": { "method": "POST", "urlPathPattern": "/wiremock/resources/add", "bodyPatterns": [ { "matchesXPath": "//resources/Id/[contains(text(),'02322')]" } ] }, "response": { "status": 202, "headers": { "Message-Request-Id": "R2{{randomValue length=4 type='NUMERIC'}}" } }, "serveEventListeners": [ { "name": "recordState", "parameters": { "context": "hardContext", "list": { "addFirst": { "resId": "{{xPath request.body '//resources/hkId/text()'}}" } } } } ] }, { "priority": 2, "request": { "method": "GET", "urlPathPattern": "/wiremock/resources/get", "customMatcher": { "name": "state-matcher", "parameters": { "hasContext": "hardContext" } } }, "response": { "status": 200, "bodyFileName": "response/resourceDetails.xml", "headers": { "Content-Type": "application/xml", "Message-Request-Id": "REQSTBPAID432{{randomValue length=4 type='NUMERIC'}}" } }, "serveEventListeners": [ { "name": "deleteState", "parameters": { "context": "hardContext", "list": { "deleteFirst": true } } } ] } ] } resourceDetails.xml: <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <Document> <Tag1> <Tag3> <MsgId>33393918</MsgId> </Tag3> <Tag2> <OrgnlResourceId>{{state context='hardContext' list='[0].resId' default='[]'}}</OrgnlResourceId> </Tag2> </Tag1> </Document>

@Dirk Bolte, Do you think any persistence : true can work, here. As state is not getting deleted. Also as part of project, do you require whole configuration or like docker and req and Resp files or anything else.

I sent requests looking like this (varying hkid):

<resources>
    <Id>02322</Id>
    <hkId>2</hkId>
</resources>

I adapted the xpath matcher to

"bodyPatterns": [
          {
            "matchesXPath": "//resources/Id[contains(text(),'02322')]"
          }
        ]

and it exactly behaved as intended: the responses contained the hkId in reverse order. Once empty, I get the default value defined in the stub mapping (

[]

) . If you still encounter issues, please provide an isolated + reduced project including a failing test to help isolating the issue.