Hi Thorsten,
> As well I really only need to render within one and the same thread
> one after another,
that should work.
> is it safe to render recursively using ComponentRenderer within
> one and the same thread?
I assume you mean 'consecutively'? Yes, see above.
H
ComponentRenderer does support that.
My individual rendering looks like the following:
> private static String
> forSome(VwrCtxctx,
> Supplier page)
> {
> try (VwrCtxThreadScoped scopedCtx = new VwrCtxT
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
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_lud...@gmx.de wrote:
Hi,
I noticed that ComponentRenderer is directly instantiating a concrete
RequestCycle while
Hi,
On Wed, Nov 27, 2013 at 2:57 AM, Colin Rogers
colin.rog...@objectconsulting.com.au wrote:
Wicketeers,
I have a problem when using ComponentRenderer in an actual live cycle. I
assume it's not actually intended for this use, and hence the errors, but
if I explain the issue, maybe
Wicketeers,
I have a problem when using ComponentRenderer in an actual live cycle. I assume
it's not actually intended for this use, and hence the errors, but if I explain
the issue, maybe someone can suggest an alternative or a workaround.
So... we have a set of 'pages' in a pageflow
