under the hood

["Farrukhjon SATTOROV (farrukh)" <fi...@gmail.com>]

Hi everyone. I'm interesting how wicket farmework work under the hood, for
example class colling sequence or steps by web server (tomcat):
webserver->deploy->war->WicketFilter->WebApplication ? Thanks an advance.

Re: under the hood

["Farrukhjon SATTOROV (farrukh)" <fi...@gmail.com>]

Thanks Martin, i suspected this but was not sure of where the "start point"


On Mon, Oct 21, 2013 at 11:20 AM, Martin Grigorov <mg...@apache.org>wrote:

> Hi,
>
>
> On Sun, Oct 20, 2013 at 5:35 PM, Farrukhjon SATTOROV (farrukh) <
> firedandy@gmail.com> wrote:
>
> > Hi everyone. I'm interesting how wicket farmework work under the hood,
> for
> > example class colling sequence or steps by web server (tomcat):
> > webserver->deploy->war->WicketFilter->WebApplication ? Thanks an advance.
> >
>
> Wicket is Servlet based web framework.
> To run a servlet based app you need to package it in .war file. When
> deployed in any web container (like Tomcat) the container will read
> WEB-INF/web.xml to initialize the application. During the initialization
> WicketFilter#init() method is called where WebApplication class is
> instantiated. With simple words the WebApplication class is the
> configuration object of the application.
> Later when a http request comes WicketFilter#filer() method will ask the
> WebApplication to process it. The WebApplication creates WebRequest,
> WebResponse and RequestCycle instances that are available for the
> application to read/write data from/to the client.
>

Re: under the hood

[Martin Grigorov <mg...@apache.org>]

Hi,


On Sun, Oct 20, 2013 at 5:35 PM, Farrukhjon SATTOROV (farrukh) <
firedandy@gmail.com> wrote:

> Hi everyone. I'm interesting how wicket farmework work under the hood, for
> example class colling sequence or steps by web server (tomcat):
> webserver->deploy->war->WicketFilter->WebApplication ? Thanks an advance.
>

Wicket is Servlet based web framework.
To run a servlet based app you need to package it in .war file. When
deployed in any web container (like Tomcat) the container will read
WEB-INF/web.xml to initialize the application. During the initialization
WicketFilter#init() method is called where WebApplication class is
instantiated. With simple words the WebApplication class is the
configuration object of the application.
Later when a http request comes WicketFilter#filer() method will ask the
WebApplication to process it. The WebApplication creates WebRequest,
WebResponse and RequestCycle instances that are available for the
application to read/write data from/to the client.

Re: under the hood

[Jeroen Steenbeeke <j....@gmail.com>]

I'm not sure how up-to-date this is, but isn't this what you want?

https://cwiki.apache.org/confluence/display/WICKET/Request+processing+overview

If you need more details than that you should probably just dive into the
source code.

- Jeroen

PS. Google is your friend, this was the first hit for "wicket request
handling"

2013/10/20 Farrukhjon SATTOROV (farrukh) <fi...@gmail.com>

> Hi everyone. I'm interesting how wicket farmework work under the hood, for
> example class colling sequence or steps by web server (tomcat):
> webserver->deploy->war->WicketFilter->WebApplication ? Thanks an advance.
>