Hi, I decided to just go ahead and change my code to support not using /osgi/* and it seems to be going well.
I can now see that servlets are actually being handled correctly so that was a bit of panic stations on my part, sorry. Static content in the WAR file gets ignored though, but I that's to be expected since the proxy is catching all. I just created another bundle for the static content that was in my WAR and registered it against the root and that's working fine. I was going to update this thread in a couple of days when I've done all my testing, but it's looking good so far. Cheers, Chris On 8 April 2010 15:42, Sten Roger Sandvik <[email protected]> wrote: > Hi. > > > However, I'm deviating from the given example slightly by using a servlet > > mapping of /osgi/* instead of just /*. My problem is that this seems to > > stop the servlet bridge working properly. > > > > The servlet bridge was designed to "catch-all" on the root (/*). What kind > of patterns are you adding to your "internal" OSGi servlets? It's maybe an > idea to test without using /osgi/* pattern for the servlets in OSGi since > this should be relative to the ProxyServlet path. > > BR, > Sten Roger >
