On 21/02/2008, Kirk Knoernschild <[EMAIL PROTECTED]> wrote:
>
> Alin,
>
> thanx for the feedback. The URL you provided doesn't work (404 error),
> but I'm very interesting in digging deeper.


FYI, Alin has recently been doing some refactoring, the file is now here:


https://scm.ops4j.org/repos/ops4j/projects/pax/web/bundle/src/main/java/org/ops4j/pax/web/service/internal/ResourceServlet.java

HTH

thanx.
>
>
> --kirk
>
> On Feb 20, 2008, at Feb 20, 10:25 PM, Alin Dreghiciu wrote:
>
> > I hope you don't mind asking about your use case? Why don't you use
> > one of the Http Services that are based on Jetty?
> > As for deploying static file Jetty has a resource servlet that is used
> > when nothing else matches a request. The problem with it is that is
> > quite tight coupled with a web application like structure. In most
> > simple way you can implement and register a servlet (as you say this
> > works) that will use the bundle that contains the static resource to
> > find and return the static file content. Of course you have to get
> > hold of that bundle and have a mapping mechanism between the request
> > and the actual file.
> >
> > You can take a look as it is done on Pax Web:
> >
> https://scm.ops4j.org/repos/ops4j/projects/pax/web/service/src/main/java/org/ops4j/pax/web/service/internal/ResourceServlet.java
> >
> > Alin
> >
> > On Thu, Feb 21, 2008 at 5:31 AM, Kirk Knoernschild <[EMAIL PROTECTED]
> > > wrote:
> >> I've embedded Jetty in Felix, registered a servlet, and have that
> >> working. But I simply can't seem to figure out how to serve up a
> >> static html file (just a simple hello.html) where that html file is
> >> deployed in one of the bundles. Using the OSGi HttpService made this
> >> incredibly easy, so I can't help but think it's equally as easy with
> >> Jetty. But no luck so far.
> >>
> >> Anyone have ideas for me?
> >>
> >> thanx.
> >>
> >> --kirk
> >> _______________________________________________
> >> OSGi Developer Mail List
> >> [email protected]
> >> https://www2.osgi.org/mailman/listinfo/osgi-dev
> >>
> > _______________________________________________
> > OSGi Developer Mail List
> > [email protected]
> > https://www2.osgi.org/mailman/listinfo/osgi-dev
>
> _______________________________________________
> OSGi Developer Mail List
> [email protected]
> https://www2.osgi.org/mailman/listinfo/osgi-dev
>



-- 
Cheers, Stuart
_______________________________________________
OSGi Developer Mail List
[email protected]
https://www2.osgi.org/mailman/listinfo/osgi-dev

Reply via email to