Hi,

I don't know if what I'm suggesting is feasible, but woudn't be better splitting the current IRequestCycleListener into:

-a IRequestCycleListener interface with methods that use RequestCycle (onBeginRequest, onEndRequest, etc...) -a new IRequestHandlerListener interface with methods that use IRequestHandler (onRequestHandlerResolved, onRequestHandlerScheduled, etc..)

?

AbstractRequestCycleListener would implement both of them.
Just my two cents....
Hi,

Currently RequestCycle is passed to some of the methods in
org.apache.wicket.request.cycle.AbstractRequestCycleListener, others
don't have it.
Should we make it consistent and pass it always or never (the user app
can use RequestCycle.get()) ?


Reply via email to