Marius, Out of interest, have you physically ran lift in asyncweb or netty? Just thinking about the embedding possibilities...
Cheers, Tim Sent from my iPhone On 7 Oct 2009, at 19:50, "marius d." <[email protected]> wrote: > > Servlet dependencies are abstracted away by a dedicated layer from the > rest of Lift. > > LiftRules.context match { > > case c: HTTPServletContext => c.ctx // this is a ServletContext > > case _ => > > } > > > So you can take the ServletContext and do your stuff with it. But in > this case you explicitly know that you are running Lift in a JEE web > container. > > This abstraction is necessary to us in order to be able to run lift > apps in other no JEE containers (Netty, AsyncWeb, Portlets etc). > > Br's, > Marius > > On Oct 7, 8:40 pm, rintcius <[email protected]> wrote: >>> Your best bet is to go find some Java static thing that's going to >>> give you >>> the ServletContext >> >> Yes that could work, but is it an idea to make the liftServlet >> available as an object in Lift (when it has the right provider)? >> Then the servletContext can be obtained nicely via >> liftServlet.getServletContext() > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
