Unintended remove of white spaces
Hi everyone, there seems to be an "unintended" remove of white spaces in soapUI. 1) When running a request with values enclosed by white spaces (e.g. <value> abcd </value>) the leading and taili...
Forum Discussion
Hi Ole,
thanks for your quick reply.
Because of some security reasons I don't want to attach the example project here. Can you please tell me a eMail adress where I can send it to?
To your questions:
- Yes, usually I apply some WS-Security configurations (esp. SAML). But the behaviour I experienced can always be reproduced by using mocks.
I also have some additional info to my point 1) of my first post:
It seems that the correct value (including white spaces) is send to the service. I could see that results were computed correctly.
But when I check the soapUI logging (remember, we always use "testrunner.bat" to start our cases and use the log option "-a") the white spaces within the logged requests are no longer there. So this seems to be a problem of logging only.
e.g.:
We send:
But this is logged as request
Best regards
Nico
thanks for your quick reply.
Because of some security reasons I don't want to attach the example project here. Can you please tell me a eMail adress where I can send it to?
To your questions:
- Yes, usually I apply some WS-Security configurations (esp. SAML). But the behaviour I experienced can always be reproduced by using mocks.
I also have some additional info to my point 1) of my first post:
It seems that the correct value (including white spaces) is send to the service. I could see that results were computed correctly.
But when I check the soapUI logging (remember, we always use "testrunner.bat" to start our cases and use the log option "-a") the white spaces within the logged requests are no longer there. So this seems to be a problem of logging only.
e.g.:
We send:
<n3:titel> a </n3:titel>
But this is logged as request
<n3:titel>a</n3:titel>
Best regards
Nico
