Hi everyone. I'm trying to run Sling in ServiceMix Kernel (uses pax-web-bundle 0.4.1). It deploys correctly, but when the SlingMainServlet tries to process a request it ends up in an infinite loop. I downgraded Pax to use the 0.2.3 version, and it works fine. My problem is that this version of Pax Web Extender tries to deploy .war files in the root of the context path (where Sling already has deployed the SlingMainServlet). So my doubts are:
1) Is Sling prepared to use a higher version of Pax than 0.2.3? According to this [1] it should, but I don't know why it's not working for me. 2) Is there some way to publish the SlingMainServlet in a different context path than "/"? I've seen it hard wired to it, but I guess it may be a good idea to have it configurable in case Sling lives in a container with other web applications (such as my case in ServiceMix Kernel). Hope someone can help. Thanks in advance. Sebastian Gomez. [1] http://www.mail-archive.com/[email protected]/msg07170.html
