You are correct. I need to make this adjustment today. Thanks for
pointing this out Tim.
Br's,
Marius
On Oct 8, 2:05 pm, Timothy Perrett <timo...@getintheloop.eu> wrote:
> Marius,
>
> Im not sure that will work as ctx is a paramater, not a val paramater.
>
> class HTTPServletContext(ctx: ServletContext) extends HTTPContext
>
> In order to do what you'd suggested wouldnt it need to be:
>
> class HTTPServletContext(val ctx: ServletContext) extends HTTPContext
>
> Thoughts?
>
> Cheers, Tim
>
> On Oct 7, 7:50 pm, "marius d." <marius.dan...@gmail.com> 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 <rintc...@gmail.com> 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 liftweb@googlegroups.com
To unsubscribe from this group, send email to
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/liftweb?hl=en
-~----------~----~----~----~------~----~------~--~---
