@Path and regex
CXF allows the use of extended regular expressions in it's @Path allowing you to create rest URIs such as:
/rest/query/{queryId:\d+}
Which would match queryId against only digits
SoapUI doesn't know what do with the \d+ and hence encodes the whole string instead of substituting during the request. BUT when it creates the form/request in the UI, it does extract queryId out as a parameter.
When it submits the request it looks like this:
/rest/query/%7BqueryId:%5Cd%2B%7D
/rest/query/{queryId:\d+}
Which would match queryId against only digits
SoapUI doesn't know what do with the \d+ and hence encodes the whole string instead of substituting during the request. BUT when it creates the form/request in the UI, it does extract queryId out as a parameter.
When it submits the request it looks like this:
/rest/query/%7BqueryId:%5Cd%2B%7D