On Mon, 08 Dec 2008, James Carman wrote:
> I believe you also have to make sure you call setOutputMarkupId(true)
> so that you make sure wicket spits out the markup id (so that it can
> select it as part of the Ajax update).
setOutputMarkupPlaceholderTag(true) already does that (see its
implementa
ack]] a was not found while trying to
> perform markup update. Make sure you called component.setOutputMarkupId(true)
> on the component whose markup you are trying to update.
>
> How about setOutputMarkupPlaceholderTag(true)?
>
> On Mon, Dec 8, 2008 at 9:20 PM, Jeremy Thomerson
found while trying to
perform markup update. Make sure you called component.setOutputMarkupId(true)
on the component whose markup you are trying to update.
How about setOutputMarkupPlaceholderTag(true)?
On Mon, Dec 8, 2008 at 9:20 PM, Jeremy Thomerson
<[EMAIL PROTECTED]> wrote:
>
> Ther
How about setOutputMarkupPlaceholderTag(true)?
On Mon, Dec 8, 2008 at 9:20 PM, Jeremy Thomerson
<[EMAIL PROTECTED]> wrote:
>
> There's another method that you need to set true on construction - I can't
> remember the exact name now, but it's something like
> setTransparentPlaceholder or somethin
There's another method that you need to set true on construction - I can't
remember the exact name now, but it's something like setTransparentPlaceholder
or something. Basically it's because the feedback panel isn't visible on the
first rendering because there's no messages. Therefore, it's no
