rating through all MarkupElements of the
>> markup of a component each time it's onInitialize is called but I
guess
>> it's not that much of an issue. I was hoping to 'piggy back' the
>> processing onto some other process that is already iteratin
of a component each time it's onInitialize is called but I guess
> it's not that much of an issue. I was hoping to 'piggy back' the
> processing onto some other process that is already iterating the markup
> elements but I haven't found a suitable spot for that yet.
7;t found a suitable spot for that yet.
>-Original Message-
>From: Igor Vaynberg [mailto:igor.vaynb...@gmail.com]
>Sent: Saturday, 24 November 2012 12:33 PM
>To: users@wicket.apache.org
>Subject: Re: Ideas on implementing dynamic addition of components that
use
>AJAX?
>
>On Thu
On Thu, Nov 22, 2012 at 11:46 PM, Martin Grigorov wrote:
> Hi,
>
>
> On Fri, Nov 23, 2012 at 9:33 AM, Chris Colman
> wrote:
>
>> >starting with wicket 1.5, however, components are able to resole their
>> >markup earlier in their lifecycle. the reason auto resolved components
>> >are added so late
arsing of the markup -
> or would that be happening too late in the lifecycle to work?
>
> > -Original Message-
> > From: Martin Grigorov [mailto:mgrigo...@apache.org]
> > Sent: Friday, 23 November 2012 6:47 PM
> > To: users@wicket.apache.org
> > Subject:
nal Message-
> From: Martin Grigorov [mailto:mgrigo...@apache.org]
> Sent: Friday, 23 November 2012 6:47 PM
> To: users@wicket.apache.org
> Subject: Re: Ideas on implementing dynamic addition of components that
use
> AJAX?
>
> Hi,
>
>
> On Fri, Nov 23, 2012
>historically the components you add from auto resolvers are added via
>the autoAdd() method, not using add(). these components only exist
>during render of the page (in detach() phase all auto-added components
>are removed). the thinking here is that auto resolved components are
>not normal compon
Hi,
On Fri, Nov 23, 2012 at 9:33 AM, Chris Colman
wrote:
> >starting with wicket 1.5, however, components are able to resole their
> >markup earlier in their lifecycle. the reason auto resolved components
> >are added so late and treated specially was because the markup was
> >only available dur
The markup is parsed already, see Component#getMarkup().
Sven
On 11/23/2012 08:33 AM, Chris Colman wrote:
starting with wicket 1.5, however, components are able to resole their
markup earlier in their lifecycle. the reason auto resolved components
are added so late and treated specially was bec
>starting with wicket 1.5, however, components are able to resole their
>markup earlier in their lifecycle. the reason auto resolved components
>are added so late and treated specially was because the markup was
>only available during render. if you are using 1.5 or 6 you can build
>your own mecha
historically the components you add from auto resolvers are added via
the autoAdd() method, not using add(). these components only exist
during render of the page (in detach() phase all auto-added components
are removed). the thinking here is that auto resolved components are
not normal components.
11 matches
Mail list logo
