Not really - can you debug JettyHTTPServerEngine and check if this
property is actually recognized at runtime.
FYI, I'm only assuming that update I was referring to is relevant, might
not be.
So start with confirming this property is indeed seen as being set, in
JettyHTTPServerEngine.shouldCheck
Thanks for reply . I have added the system property as you suggest but there
is no difference .Can you please suggest me if have any other way to get
out of the problem.
Cheers,
ravi
--
View this message in context:
http://cxf.547215.n5.nabble.com/conflicts-with-the-registered-path-tp5766073p
Hi
I recall there was some work added to avoid some side-effects related to
running multiple CXF Jetty endpoint on the overlapping paths, but then
it caused issues for some existing deployments (like yours) so a property
"org.apache.cxf.transports.http_jetty.DontCheckUrl" was added.
It can b
Thank you.
>
> Regards
> Raman
>
> -Original Message-
> From: Sergey Beryozkin [mailto:sberyoz...@gmail.com]
> Sent: Wednesday, October 08, 2014 2:53 PM
> To: users@cxf.apache.org; d...@cxf.apache.org
> Subject: Re: conflicts with the registered path
>
> Hi
>
>
That helps. We will wait for 3.0.2.
Thank you.
Regards
Raman
-Original Message-
From: Sergey Beryozkin [mailto:sberyoz...@gmail.com]
Sent: Wednesday, October 08, 2014 2:53 PM
To: users@cxf.apache.org; d...@cxf.apache.org
Subject: Re: conflicts with the registered path
Hi
Redirecting
Hi
Redirecting to the users list
Apparently supporting overlapping addresses was causing issues in other
cases where the Jetty transport was used and it was restricted in 3.0.1.
CXF 3.0.2 (the release process is about to start) has a
"org.apache.cxf.transports.http_jetty.DontCheckUrl" system
