@wicket.apache.org users@wicket.apache.org
Date: 03/11/2011 01:00 AM
Subject:RE: Wicket thinks setOutputMarkupId property is not set to
true
Hmmm, it is in a tab panel so it could be the scenario you mention. I'll
check out that theory.
Chris
-Original Message-
From
Note, I'm referring to ajax-tab-panels which are ajax ready by default...
From: mzem...@osc.state.ny.us
To: users@wicket.apache.org
Date: 03/11/2011 03:11 PM
Subject:RE: Wicket thinks setOutputMarkupId property is not set to
true
I've run into this using tab-panels, you have
I get this error even though I set output markup ID to true on the component
that is being replaced (and the one that is replacing it):
Root cause:
java.lang.IllegalArgumentException: cannot update component that does not have
setOutputMarkupId property set to true. Component:
: Wicket thinks setOutputMarkupId property is not set to true
I get this error even though I set output markup ID to true on the component
that is being replaced (and the one that is replacing it):
Root cause:
java.lang.IllegalArgumentException: cannot update component that does not have
To: users@wicket.apache.org
Subject: Wicket thinks setOutputMarkupId property is not set to true
I get this error even though I set output markup ID to true on the component
that is being replaced (and the one that is replacing it):
Root cause:
java.lang.IllegalArgumentException: cannot update
: Friday, 11 March 2011 4:02 PM
To: users@wicket.apache.org
Subject: Wicket thinks setOutputMarkupId property is not set to true
I get this error even though I set output markup ID to true on the component
that is being replaced (and the one that is replacing it):
Root cause
