On Tue, May 22, 2012 at 12:40 AM, Marius Giepz
<[email protected]> [1]wrote:
Thanks for your suggestions, Reto! Am 16.05.2012 16:15, schrieb Reto
Bachmann-Gmür: As far as I know the mechanism by which the servlet
filter is registered
is supported only by the felix http service. The servlet filter is
just registered as a service and annotated with some properties. So I
guess that a different http-service being used is the reason things
don't work in your karaf setting.
You are right in so far as sling-standalone uses
org.apache.felix.http.jetty to provide
org.osgi.service.http.**HttpService whereas karaf uses
org.ops4j.pax.web.pax-web-**runtime. I would support you assumption if
i didnt have the case where it works with sling 2.0.6 and Karaf 2.2.7
(which has the pax-web httpservice)
I'm wondering what works with the pax-web httpservice. Sling-rs
resources should work independently of the the servlet-filter
registration mechanism. Jax-rs resources will only work if the filter
is registered with the http-service. Cheers, Reto
I will try to debug and see why it works/doesnt work under certain
configurations.
The Pax stuff is kinda weird. i.e. it Pax-Loggin claims to export
org.apache.log4j 1.2.15
but some methods have a different signature compared to
log4j-1.2.15.jar :/
The Sling-Rs is useless for my scenario as it is sort of a "crippled"
Jax-Rs. It
doesnt seem to support @Path.
regards,
Marius
Links:
------
[1] mailto:[email protected]
