wicket only knows that the component needs it when you add it to the ajax request target. by the time you add it to the ART the component has already been rendered into the browser during the previous request, and so its too late at this point - all we can do is warn you.
-igor On Fri, Oct 3, 2008 at 11:01 AM, Mathias P.W Nilsson <[EMAIL PROTECTED]> wrote: > > Hi! > > I don't know if this has already been answered but here it goes. > > When use Ajax with wicket you have to set the the component to output it's > markup id or else wicket framework complains about not having it set. Now > Why isn't the components markup set automatically > when wicket knows about it? Why not skip this, for ajax anyway. If you want > to do some other javascript the output it but otherwise wicket could take > care of it or maybe I'm missing something. > > // Mathias > -- > View this message in context: > http://www.nabble.com/setOutputMarkupId-and-Ajax-tp19802839p19802839.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
