Forum Discussion
bonsino
12 years agoNew Contributor
Hi,
I can confirm that this is a bug! I've reproduced it with SoapUI 4.5.1, 4.6.2 and 4.6.3. When I change the endpoint of the request from JMS to a HTTP-Endpoint property expansion works.
When will this get fixed? Any workarounds?
I can confirm that this is a bug! I've reproduced it with SoapUI 4.5.1, 4.6.2 and 4.6.3. When I change the endpoint of the request from JMS to a HTTP-Endpoint property expansion works.
When will this get fixed? Any workarounds?