At least for Wicket 1.4, you can take a look at the internal method org.apache.wicket.RequestCycle.steps(). Basically, this is the place where a request that has been identified as a request to the Wicket application goes through the corresponding steps in the Wicket request processing cycle. At the beginning of the class, the RequestCyclemain steps are represented by each int constant. The higher the int value, the later the step enters the loop. The method RequestCycle.step()that is called from RequestCycle.steps()has a switch statement to delegate the various steps to the responsible infrastructure methods, which are delegated further.
The steps or phases, if you wish, are in order in the request loop:
- NOT_STARTED - initial value
- PREPARE_REQUEST - preparation for further processing, calls onBeginRequest
- RESOLVE_TARGET - Define the appropriate request target
- PROCESS_EVENTS - , RESPOND
- RESPOND - ,
- DETACH_REQUEST -
- DONE - DETACH_REQUEST
, , , IRequestCycleProcessor IRequestTarget.