@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 should add that this is on 1.5-rc2. Previously on 1.4.16 the exact same code
(except for package renames) worked fine.
Chris
-Original Message-
From: Coleman, Chris [mailto:chris.cole...@thalesgroup.com.au]
Sent: Friday, 11 March 2011 4:02 PM
To: users@wicket.apache.org
Subject:
You did say that you set output markup ID to true on both components,
but maybe you should double check that. I had a very similar problem
once with an AjaxTabbedPanel that went like this:
1-The first displayed panel (tab) did not have setOutputMarkupId(true);
2-When the second tab is selected
setOutputMarkupId property is not set to true
You did say that you set output markup ID to true on both components,
but maybe you should double check that. I had a very similar problem
once with an AjaxTabbedPanel that went like this:
1-The first displayed panel (tab) did not have setOutputMarkupId(true);
2
