You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@wicket.apache.org by Sven Ludwig <s_...@gmx.de> on 2014/04/29 19:08:06 UTC

IRequestCycleProvider and ComponentRenderer

Hi,

I noticed that ComponentRenderer is directly instantiating a concrete RequestCycle while in the Application there is an abstract factory mechanism based on IRequestCycleProvider.

Could the flexibility of having a custom RequestCycle be provided for ComponentRenderer as well?

Kind Regards,
Sven

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org

Re: IRequestCycleProvider and ComponentRenderer

Posted by Martin Grigorov <mg...@apache.org>.

https://issues.apache.org/jira/browse/WICKET-5574
Thanks for reporting!

Martin Grigorov
Wicket Training and Consulting


On Tue, Apr 29, 2014 at 7:08 PM, Sven Ludwig <s_...@gmx.de> wrote:

> Hi,
>
> I noticed that ComponentRenderer is directly instantiating a concrete
> RequestCycle while in the Application there is an abstract factory
> mechanism based on IRequestCycleProvider.
>
> Could the flexibility of having a custom RequestCycle be provided for
> ComponentRenderer as well?
>
> Kind Regards,
> Sven
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>