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

Posted to dev@wicket.apache.org by Igor Vaynberg <ig...@gmail.com> on 2011/09/27 18:05:07 UTC

a proposal to automate output of markup ids

ive come up with a simple proposal to eliminate the need to call
setoutputmarkupid(true) on components. it is here:
https://issues.apache.org/jira/browse/WICKET-4091

your feedback is welcome, especially if something like this will
totally hose your application. if we choose to do this it wont be done
until wicket.next .

-igor

Re: a proposal to automate output of markup ids

Posted by Dan Retzlaff <dr...@gmail.com>.

Your proposal seems reasonable to me. Even if it somehow introduces
a superfluous markup ID, it's hard to imagine how that would hose an
application.

That said, it won't actually eliminate most of our app's
setOutputMarkupId(true) calls. I thought you were going to propose some
runtime bytecode magic to see if a component instance and AjaxRequestTarget
might ever meet. :)

Dan

On Tue, Sep 27, 2011 at 9:05 AM, Igor Vaynberg <ig...@gmail.com>wrote:

> ive come up with a simple proposal to eliminate the need to call
> setoutputmarkupid(true) on components. it is here:
> https://issues.apache.org/jira/browse/WICKET-4091
>
> your feedback is welcome, especially if something like this will
> totally hose your application. if we choose to do this it wont be done
> until wicket.next .
>
> -igor
>