Hi Sergey,
I was a bit busy, I finally could verify all the changes and hints that you
mentioned today.
I tried all the options in question and I think that the issues are gone.
The deployment was somewhat bold:
- One web application with the web.xml with a single JAX-RS servlet mapped to
/*,
Hi Sergey.
> I think one solution can be to combine resources and providers from multiple
> applications
> into a single application and serve it on a single servlet, not sure it will
> make sense
> in your case though, but this is something I'd try.
I was thinking about this possibility as w
Hi Sergey,
thank you for the conclusion - it's good to know what the situation is. I hope
that you'll find a solution eventually.
For the time being I tried using ApplicationPath as the only working solution.
However, it has one really funny side-effect. The paths to the services contain
an ex
ult CXF Servlet in OSGI Blueprint?
Regards,
Andrei.
> -Original Message-----
> From: Dolezal, Petr [mailto:petr.dole...@atos.net]
> Sent: Mittwoch, 23. April 2014 14:21
> To: users@cxf.apache.org
> Subject: RE: Troubles with multiple JAX-RS applications in one web.xml
>
Hi Sergey.
> The question though remains, given that you use web.xml, no Spring &
> Blueprint,
> meaning that in case of a single web.xml you have two
> CXFNonSpringJaxrsServlet
> instances created, how both of those instances end up sharing the bus (lets
> say
> the same endpoint registry in
Hi Sergey,
you were a bit faster than me with my reply :-) Well, I mentioned it in my
original post: we use an OSGi container (Equinox) with embedded Jetty. So the
code base is indeed shared. It looks you are confirming my impression that CXF
shares some information globally, which is not worki
Hi Sergey,
thanks for the explanation. We will try to use ApplicationPath then when there
is no other way.
However, there remains one thing that still confuses me and it still looks like
a bug or something unexpected at least. You wrote:
> Using ApplicationPath is indeed the only way to have m
issues.apache.org/jira/browse/CXF-5702,
one will need to set "jaxrs.application.address.ignore" servlet parameter to
"false" in CXF 3.0.0 given that by default the servlet pattern is expected to
override ApplicationPath.
HTH, Sergey
On 22/04/14 11:34, Dolezal, Petr wrote:
> I&
I've got an additional information from my colleague. He tried as a work-around
to split the web application. Hence he deployed two web applications, each
containing just one of the two parts from the original web.xml. So, the backup
plan does not work and it is definitely a problem.
There is s
Hello,
it seems that it is not possible to have multiple JAX-RS servlets in one
web.xml. Only the first one accessed becomes available, the others throw an
exception and no jaxrs.* init parameters have any influence. I'm using CFX
3.0.0.milestone2.
The situation:
I'm trying to deploy a RESTful
eryoz...@gmail.com]
Sent: Wednesday, February 19, 2014 5:59 PM
To: users@cxf.apache.org
Subject: Re: JAX-RS with CXF and Equinox: a class loader problem?
Hi
On 19/02/14 13:40, Dolezal, Petr wrote:
> Hi,
>
> thanks for a quick response. I tried your suggestion. Well, it appears that
> it
Hi,
thanks for a quick response. I tried your suggestion. Well, it appears that it
heals just one of many places - calling getExtension(ClassLoader.class) does
not look like a rare thing. I found two more on the invocation path to our web
service:
org.apache.cxf.transport.servlet.ServletContro
Hello,
I encountered a class loading problem using CXF as the JAX-RS implementation in
Equinox OSGi container. It seems that CXF, deep in its core, triggers
unfortunately some Equinox-specific stuff that results later in the problems. I
have no idea how to solve it and I would be thankful for a
13 matches
Mail list logo
