Your guess is rightthank you for the help
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Wicket-cannot-find-id-in-inner-enclosure-but-has-no-problem-in-outer-one-tp4559666p4568555.html
Sent from the Users forum mailing list archive at Nabble.com.
Hi, can anyone tell me any other alternative of enclosure if the above
problem cant be bugged out??
You can do explicitly what the enclosure does more conveniently, by using a
WebMarkupContainer where isvisible() delegates to the child's isVisible().
- Tor Iver
See org.apache.wicket.markup.html.basic.EnclosureContainer
On Tue, Apr 17, 2012 at 9:48 AM, Wilhelmsen Tor Iver toriv...@arrive.no wrote:
Hi, can anyone tell me any other alternative of enclosure if the above
problem cant be bugged out??
You can do explicitly what the enclosure does more
I have removed inner enclosure and its working fine. I am facing another
problem. This is my code:
ChoiceRendererSelectOption choiceRenderer = new
ChoiceRendererSelectOption(value, key);
SelectOption selectedOption = new
SelectOption(selectOption[0].getKey(), Selected Value);
Hey there,
This is just a guess!!
Why are you creating a new SelectOption?;
SelectOption selectedOption = new
SelectOption(selectOption[0].getKey(), Selected Value);
when you could just use the one that exists (selectOption[0])? The
PropertyModel doesn't make sense, ether. I'd remove
Hi, can anyone tell me any other alternative of enclosure if the above
problem cant be bugged out??
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Wicket-cannot-find-id-in-inner-enclosure-but-has-no-problem-in-outer-one-tp4559666p4562050.html
Sent from the Users
