Re: Setting up Http Servlet Bridge (relative paths)

Hi - it took some time, but I’ve created an issue for this now: https://issues.apache.org/jira/browse/FELIX-5219 Best Regards //Anders > On 16 Feb 2016, at 07:26, Carsten Ziegeler wrote: > > This definitely sounds like a bug in the new versi

Re: Setting up Http Servlet Bridge (relative paths)

This definitely sounds like a bug in the new version. Patches are welcome :) Thanks Carsten Anders Engström wrote > Hi again - > > One thing that differs between the jackrabbit standalone-sample and my sample > code is the *version* of the http proxy/bridge libraries. > > I’m using org.apache.

Re: Setting up Http Servlet Bridge (relative paths)

Hi again - One thing that differs between the jackrabbit standalone-sample and my sample code is the *version* of the http proxy/bridge libraries. I’m using org.apache.felix.http.proxy/3.0.0 and org.apache.felix.http.bridge/3.0.6 - in your sample both those libraries are at version 2.3.2. Gue

Re: Setting up Http Servlet Bridge (relative paths)

Thanks a lot for replying! I’ll dig into the oak-standalone sample code to see what’s different from my sample application. I’ve added the Felix WebConsole to my sample app @ https://github.com/metamorph/http-osgi-bridge/tree/add-felix-webconsole

Re: Setting up Http Servlet Bridge (relative paths)

HI Anders, > Everything seems to work, if I register servlets (in the OSGi container) to > the path `/bundles/{servlet}`. That is — the OSGi component registering the > Servlet *needs* to know to which context path the proxy servlet is mapped. Have a look at [1] where there ProxyServlet is regi

Re: Setting up Http Servlet Bridge (relative paths)

Hi again - I guess it’s just me that’s having problems with this (judging from the number of replies) *smile*. So, I get the behaviour I need if I drop the servlet-path from the request. That way a request to the proxy-servlet on “//proxy-servlet/foo” ends up as a call to `org.apache.felix.ht

Re: Setting up Http Servlet Bridge (relative paths)

Thanks for the link, Carsten - I’ve had a look and, as you mentioned, the way Sling is mounting servlets isn’t comparable to how it’s done in a straight forward web-app. I’ve been digging through the code of org.apache.felix.http.(proxy | bridge) and debugging to see how it all fits together.

Re: Setting up Http Servlet Bridge (relative paths)

Anders Engström wrote > Hi, thanks for replying - > > that’s interesting.. code you provide a pointer to some sample code? The code for Sling can be found at: http://svn.apache.org/repos/asf/sling/trunk/launchpad/base/ It's a whole module and more complicated than what you probably need, but m

Re: Setting up Http Servlet Bridge (relative paths)

Hi, thanks for replying - that’s interesting.. code you provide a pointer to some sample code? /Anders > On 04 Feb 2016, at 16:45, Carsten Ziegeler wrote: > > Hi, > > I dont know the details, but we use the bridge in Apache Sling and in > some other projects. And if we register a servlet at

Re: Setting up Http Servlet Bridge (relative paths)

Hi, I dont know the details, but we use the bridge in Apache Sling and in some other projects. And if we register a servlet at /demo it's not directly reachable at /demo, but /context/{servlet}/demo Carsten Anders Engström wrote > Hi - > > I’m trying to set up the Felix Servlet Bridge in Tomcat

Setting up Http Servlet Bridge (relative paths)

Hi - I’m trying to set up the Felix Servlet Bridge in Tomcat (8) as a proxy to a bunch of services running in an embedded OSGi container. I’ve registered the `org.apache.felix.http.proxy.impl.ProxyServletContextListener` in web.xml and I’ve got a servlet setup that uses the `org.apache.felix