Just double checked that using WebClient directly (in that test I
pointed out to) works as well. So IMHO the problem is somewhere at the
lower level.
Sergey
On 07/04/16 12:24, Sergey Beryozkin wrote:
Hi
One thing I'd like to point out - CXF checks the matrix parameters on
the request URI,
Hi
One thing I'd like to point out - CXF checks the matrix parameters on
the request URI, obtained from:
(HttpServletRequest)req.getRequestURI();
which must not return the query part.
So the source of the problem is that either:
- the container mistakenly returns the query as part of the
Hi Christian
I simply updated this test:
https://github.com/apache/cxf/blob/master/systests/jaxrs/src/test/java/org/apache/cxf/systest/jaxrs/JAXRSClientServerBookTest.java#L1954
I tried
"http://localhost:; + PORT +
"/bookstore/segment/matrix;first=12;second=3?loc=123"
and only with a
Hi Sergey,
Thank you for looking into this. We are using an internal framework at
work that makes use of CXF - which means that it's not that easy to
just swap CXF out, unfortunately.
Having said that, a colleague started work to replace CXF 2.x by CXF
3.x today. But it'll be a few days before
Hi
I've experimented with a local test, I can not reproduce it.
Can you please add some logging on the client/server, or preferably,
pass it via some TCP tracer, I wonder if the question mark ends up being
encoded, etc, may be the client (HttpUrlConnection) gets confused about
PUT and query
Hi all,
We are restricted to the 2.x branch of cxf.
When we call our REST endpoint and provide a matrix parameter
(;id=123), followed by a query parameter (?loc=abc), cxf populates the
String argument annotated with the @MatrixParam bind annotation with
the merged String of matrix value and
