cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jérôme Revillard <jrevill...@gnubila.fr>
Subject Re: CXF + Karaf 4: how to access the CXFNonSpringServlet
Date Fri, 14 Aug 2015 12:24:25 GMT
Thanks Sergey,

I would really like to be be able to fix my issue because it seems to be 
the "cleanest" way of doing what I want to achieve even if it's a bit 
more complex.
Would you have an idea ?

Best,
Jerome

Le 14/08/2015 13:49, Sergey Beryozkin a écrit :
> Hi
>
> I did try disabling the default servlet in one of the demos. But I 
> used CXFBlueprintServlet instead and registered the bundle as a war 
> bundle, without having to create the analog of the default CXF 
> Transport - appears to be a complex path.
>
> For example:
>
> https://fisheye6.atlassian.com/browse/cxf/systests/jaxrs/src/test/resources/jaxrs_soap_blueprint/WEB-INF/web.xml?r=d2fc5e244b042a47c84c57426f74cb589501489e

>
>
> that is a link to a non-osgi test, but the same worked for me in 
> Karaf, I only used an aries blueprint-web-osgi bundle to support it
>
> Cheers, Sergey
>
> On 14/08/15 12:40, Jérôme Revillard wrote:
>> 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
>>>
>>> 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 ?
>>>
>>> Sergey
>>> On 14/08/15 10:31, jrevillard wrote:
>>>> 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
>> =====================================================
>>
>

-- 
=====================================================
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
=====================================================



Mime
View raw message