[
https://issues.apache.org/jira/browse/CXF-7783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16534365#comment-16534365
]
Andriy Redko commented on CXF-7783:
-----------------------------------
Hi [~Alexander.Onnikov], I remember these kind of issues ... So you are doing
everything right but there is an issue with Atm (underlying Websocket transport
in CXF): it does set the request context path to first component (in this case,
/demo, nonetheless it should be set to /demo/error). For now I don't have an
easy solution to this except keeping /demo as the context path and making
/error the part of JAX-RS resource, f.e. /error/customerservice/customers.
Thanks.
> JAX-RS Server fails to serve requests via Websocket transport when context
> path is long
> ---------------------------------------------------------------------------------------
>
> Key: CXF-7783
> URL: https://issues.apache.org/jira/browse/CXF-7783
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS, Transports
> Affects Versions: 3.2.5
> Reporter: Alexander Onnikov
> Priority: Minor
>
> I played with JAX-RS Websocket example and noticed that it does not work as
> expected when context path consists of several sections.
> https://github.com/apache/cxf/blob/master/distribution/src/main/release/samples/jax_rs/websocket/src/main/java/demo/jaxrs/server/Server.java#L27
> I modified CONTEXT_PATH to be "/demo/error" then started demo server and
> established websocket connection to "ws://localhost:9000/demo/error". It was
> success but all requests failed:
> I tried following requests:
> GET /demo/error/customerservice/customers/123 (returned 404)
> GET /error/customerservice/customers/123 (returned 400)
> GET /customerservice/customers/123 (returned 400)
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
