LiftFilter is indeed only extending ServletFilterProvider which is
oriented obviously for JEE servlet filter processing (we do this for
backward compatibility reasons). ServletFilterProvider is also
extending HTTPProvider which knows about LiftServlet.
ServletFilterProvider just calls the service function and from here
the LiftServlet gets called. HTTPProvider trait has no knowledge about
servlets API, neither LiftServlet which is not a real JEE servlet.
Br's,
Marius
On Sep 18, 7:03 pm, Meredith Gregory <lgreg.mered...@gmail.com> wrote:
> Dear Lifted,
> bash-3.2$ cd liftweb/
> bash-3.2$ ls
> builtin http sitemap
> bash-3.2$ find . -name *.scala -exec grep "LiftFilter" '{}' \; -print
> class LiftFilter extends ServletFilterProvider
> ./http/LiftServlet.scala
> * @see LiftFilter
> ./http/S.scala
> bash-3.2$
>
> The web.xml file references LiftFilter. The class LiftFilter extends the
> Java class ServletFilterProvider and has no body. It looks like all the
> logic is in LiftServlet. What makes the connection?
>
> Best wishes,
>
> --greg
>
> --
> L.G. Meredith
> Managing Partner
> Biosimilarity LLC
> 1219 NW 83rd St
> Seattle, WA 98117
>
> +1 206.650.3740
>
> http://biosimilarity.blogspot.com
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
