Hi, Not having tested it, but you might want to consider the Pax Web project [1]. The have both an OSGi HttpService implementation and an extender based on Jetty 6.
Regards Felix [1] http://wiki.ops4j.org/display/paxweb/Pax+Web On 03.09.2010 17:03, Victor Taranenko wrote: > I think native spring dm web extender not imlements OSGi HttpService > interface, so it is not good for a sling framework. > > 2010/9/3 Justin Edelson <[email protected]> > >> If you wanted to use Spring DM's web extender, you could simply remove >> the Felix HttpService implementation and replace it with one of the >> implementations from SpringDM. >> >> I have not done this myself, but I believe it would work. >> >> Justin >> >> On 9/2/10 11:59 PM, Victor Taranenko wrote: >>> Hi Ruben. >>> About few weeks ago I've successfuly integrated spring application with >>> Sling framework through Spring Dynamic Modules. If you want use only >> spring >>> framework core libraries, i think that there are should no any problems. >> But >>> if you want to user Spring-MVC inside Sling you need to do some little >> magic >>> (as I understand). Spring DM web-extender requires a shared application >>> server instance (Jetty or Tomcat) inside OSGi environment. But default >> Sling >>> HttpService based on Jetty encapsulates it. So I decided to use separate >>> Tomcat server instance nearby existing Jetty and register it in OSGi >>> environment. It helps me, but I think that it's not very good. So if find >>> better solution please put it into this thread. >>> >> >> > >
