This message was deleted.
# helps
Slackbot
09/29/2023, 6:14 PMThis message was deleted.
d
Debraj Manna
09/29/2023, 6:42 PMI was sending a malformed json request
l
Lee Turner
09/29/2023, 7:48 PMSo it is working now ?
m
Maxim Bastrygin
10/04/2023, 8:59 AMNo, it seems it is not. Have the same issue using version 2.33.1. The only difference is I am using "&&".
d
Debraj Manna
10/04/2023, 8:59 AM@Lee Turner It is working for me after fixing the json
m
Maxim Bastrygin
10/04/2023, 9:00 AM@Debraj Manna How did you fix it?
d
Debraj Manna
10/04/2023, 9:01 AMMy request json was malformed json. For example, in the screenshot shared above
"payload": pnr_details_responsel
Lee Turner
10/04/2023, 9:04 AM@Maxim Bastrygin Can you give examples of your requests and mappings to give us an idea of what you are trying to do ?
m
Maxim Bastrygin
10/04/2023, 9:17 AM{
fromAccountId: 123, providerId: 123, operationId: 123, paymentInformation: 123, step: 1, attributes: [{attributeName: customerCode, value: abc}, {attributeName: pinCode, value: 01.01.1900}]
}
"bodyPatterns": [
{
"matchesJsonPath": "$.attributes[?(@.attributeName == 'customerCode' && @.value == 'abc')]"
}
]
l
Lee Turner
10/04/2023, 9:21 AMQuick question, your json isn’t valid. Is that what you are using or is that just a copy/paste issue into slack ?
Lee Turner
10/04/2023, 9:23 AMThe json in the request I mean
m
Maxim Bastrygin
10/04/2023, 9:27 AMJust copied it from our front-end console
Maxim Bastrygin
10/04/2023, 9:27 AM Copy code
{
"fromAccountId": 123,
"providerId": 123,
"operationId": 123,
"paymentInformation": 123,
"step": 1,
"attributes": [
{
"attributeName": "customerCode",
"value": "abc"
},
{
"attributeName": "pinCode",
"value": "01.01.1900"
}
]
}👍 1
Maxim Bastrygin
10/04/2023, 9:27 AMThis is the valid one
l
Lee Turner
10/04/2023, 9:55 AMNot sure what the problem would be. I have just tried your payload with your
bodyPatternsm
Maxim Bastrygin
10/04/2023, 9:55 AMSo yours is 3.2.0?
Maxim Bastrygin
10/04/2023, 9:56 AMWill try to test with it then
l
Lee Turner
10/04/2023, 9:58 AMYes, I think so. Might be the release before
3.2.0Lee Turner
10/04/2023, 10:00 AMI am using wiremock standalone in docker at the moment. I normally use the nightly image. Will delete my local image to make sure I have the latest
Lee Turner
10/04/2023, 10:01 AMOK, just pulled the latest image and retested and it seems to match the request fine
🙌 1
m
Maxim Bastrygin
10/04/2023, 10:01 AMMuch obliged Lee!
l
Lee Turner
10/04/2023, 10:03 AMNo worries at all. Just for reference I am testing with a very simple get request with your
bodyPatterns Copy code
{
"name": "test",
"request": {
"url": "/test",
"method": "GET",
"bodyPatterns": [
{
"matchesJsonPath": "$.attributes[?(@.attributeName == 'customerCode' && @.value == 'abc')]"
}
]
},
"response": {
"status": 200,
"transformers": [
"response-template"
],
"jsonBody": {
"id": "{{randomInt}}",
"name": "test",
"creationDate": "{{now}}"
}
}
}Lee Turner
10/04/2023, 10:04 AMThen testing with curl:
Copy code
curl -X GET --location "<http://localhost:7777/test>" \
-H "Content-Type: application/json" \
-d "{
\"fromAccountId\": 123,
\"providerId\": 123,
\"operationId\": 123,
\"paymentInformation\": 123,
\"step\": 1,
\"attributes\": [
{
\"attributeName\": \"customerCode\",
\"value\": \"abc\"
},
{
\"attributeName\": \"pinCode\",
\"value\": \"01.01.1900\"
}
]
}"27 Views