Re: CXF + Karaf 4: how to access the CXFNonSpringServlet

[Jérôme Revillard]

Hi Sergey,

No, /test-uri does not respond (404 from jetty).

Concerning the default HTTP transport, the fact is that I creates the /cxf context myself now (I basically copy/pasted the classes from here <https://github.com/apache/cxf/tree/master/rt/transports/http/src/main/java/org/apache/cxf/transport/http/osgi> to it). So /cxf respond but, it says "No services have been found." instead of displaying the actually exposed ones that I can find inside the Karaf shell

karaf@root()> cxf:list-endpoints
Name                      State Address BusID

[TestURI ] [Started ] [/test-uri ] [fr.maatg.pandora.gateway.pandora-gateway-sal-saga-cxf1486728741] [SagaServiceJobPort ] [Started ] [/job ] [fr.maatg.pandora.gateway.pandora-gateway-sal-saga-cxf1486728741] [SagaServiceDataManagementPort] [Started ] [/data ] [fr.maatg.pandora.gateway.pandora-gateway-sal-saga-cxf1486728741] In fact, if I try to contact my test web service: https://localhost:8443/cxf/test-uri/test, it says also "No service was found." instead of displaying the service output.

Best,
Jerome

Le 14/08/2015 13:16, Sergey Beryozkin a écrit :

Hi



Sergey
On 14/08/15 10:31, jrevillard wrote:

The default HTTP transport creates a /cxf context, without it it is up to the custom application how to control the context name, does /test-uri respond, etc ?

Last but not least, my enpoints are registered:Best,Jerome



--

View this message in context: http://cxf.547215.n5.nabble.com/CXF-Karaf-4-how-to-access-the-CXFNonSpringServlet-tp5760086p5760092.html

Sent from the cxf-dev mailing list archive at Nabble.com.

--
=====================================================
Dr Jérôme Revillard
CTO MAAT/GNUBILA France
www.gnubila.fr

174 Impasse des Prés d'en Bas
74370 Argonay (France)

Mob.    0033 676 108 185
Tel.    0033 450 685 601
=====================================================

smime.p7s
Description: Signature cryptographique S/MIME