zathomas/org.ops4j.pax.wicket — comment on commit 5b2387e590db40b6514f08eb454d24d42bc0cbda
File: service/src/main/java/org/ops4j/pax/wicket/internal/ServletProxy.java line 50
By anpieber:

Great. Thx for giving me the details about this. Great to hear that the
example works out well. In case you plan too drive this any further feel
free to ping me on the ops4j list to discuss a solution how this can be
solved cleanly.

Kind regards, Andreas

Send from my mobile. Please excuse the brevity and/or possible auto
correction errors.
On Feb 7, 2012 5:50 PM, "Zach A. Thomas" <
reply@reply.github.com>
wrote:

> Sling is (among other things) an HTTP front-end to Apache Felix. It
> determines how each request should be delegated (which servlet, etc.). So
> by "claiming" a path for use by the Wicket app, Sling will delegate
> requests for that path to the right place.
>
> This isn't in production or anything. I was doing an experiment to see if
> Sling and Wicket could co-exist. The experiment works, but I haven't tried
> to take it any further.
>
> Cheers.
>
> ---
> Reply to this email directly or view it on GitHub:
>
> https://github.com/zathomas/org.ops4j.pax.wicket/commit/5b2387e590db40b6514f08eb454d24d42bc0cbda#commitcomment-941751
>