use a border instead of a panel, thats what borders are for...
-igor
On Fri, May 21, 2010 at 11:10 AM, Brian Mulholland
wrote:
> Cool, those both helped alot. Unfortunately, they have lead me to
> realize another major flaw in my plan. Of course the wicket panel is
> destroying the content in
Cool, those both helped alot. Unfortunately, they have lead me to
realize another major flaw in my plan. Of course the wicket panel is
destroying the content in the template. In most cases that is a
feature, but in this case the point is for the control to act as a
wrapper around other content (
Hi,
1)
To get wicket to output a dom id you must call
mycomponent.setOutputMarkupId(true). This will output a generated dom
id, which you can access in your java code by calling
mycomponent.getMarkupId().
Wicket will overrwrite any dom id in your code, if that element is
used for a wicket compone