Hi,
On 27/12/11 13:12, Tcharl wrote:
Hi,
Yes, I am.
But this absolute adress use a different context as the webapp one. Is that
change something?
What webapp are you talking about ? Is it the one which loads the
jaxrs:endpoint ? If yes then why do you get an absolute address, may be
you can try a relative one ?
I'm not sure what exactly is happening in your case; CXF, in its HTTP
transport module, has a Blueprint application context which creates a
default '/cxf' context by getting a handler registered with HttpService.
But that should not prevent HttpService listening on multiple contexts,
right ?
Cheers, Sergey
Date: Mon, 26 Dec 2011 07:22:20 -0800
From: [email protected]
To: [email protected]
Subject: Re: CXF, Jetty, OSGI and multiple web contexts
Hi
On 26/12/11 13:58, Tcharl wrote:
Hi,
I'm trying to make a full webapp stack on osgi.
So, I have two wars archive deployed on a single jetty server (published via
spring dm and a custom deployer).
When I start the interface war alone (the war wich does not contain cxf) and
go to http://localhost:8080/, I have the list of the available contexts.
But when I start the ws war (cxfied), I don't have this list, and only one
web context (the cxf one) is available.
How can I do to support multiple web contexts in a single jetty server
instance with cxf?
I'm wondering is it because you may be using an absolute address as you
did show in the other email ?
Cheers, Sergey
Best regards, you've made a very nice framework,
--
View this message in context:
http://cxf.547215.n5.nabble.com/CXF-Jetty-OSGI-and-multiple-web-contexts-tp5101559p5101559.html
Sent from the cxf-user mailing list archive at Nabble.com.
