Hi JS,
Well the "/cxf" is just the servlet 'alias' used when the SMX
OsgiServlet is registered with the OSGi HttpService[1].
Its currently configured via META-INF/spring/cxf-transport-osgi.xml in
the cxf-transports-osgi bundle:
<osgi:service ref="osgiServlet" interface="javax.servlet.Servlet">
<osgi:service-properties>
<entry key="alias" value="/cxf" />
<entry key="servlet-name" value="cxf-transport-osgi-servlet"/>
</osgi:service-properties>
</osgi:service>
So I guess this alias could be over-ridden to something more
implementation-agnostic if you find it objectionable.
Cheers,
Eoghan
[1] http://www.osgi.org/javadoc/r4v41/org/osgi/service/http/HttpService.html
2009/4/21 jsbournival <[email protected]>:
>
>
> Eoghan Glynn-4 wrote:
>>
>> BTW in addition to the fix for SMX4-278, I believe you'll also need to
>> change your @Path annotation from:
>>
>> �...@path("/")
>>
>> to:
>>
>> �...@path("/cxf/news")
>>
>
> Ok now this is strange. It means that my service is now bound to CXF
> implementation. This "/cxf" prefix is not making any sense on top of
> Jersey/RestEasy/...
>
> Also, the @Path annotation can no longer represent a resource, strictly
> speaking.
>
> What are your thoughts on that?
>
> JS.
> --
> View this message in context:
> http://www.nabble.com/Deploying-REST-service-on-CXF-Transport-for-OSGi-fails-tp23164054p23164896.html
> Sent from the cxf-user mailing list archive at Nabble.com.
>
>
