Hi,
Finally I got solved the problem and I wanna share with you. My
checkgroup in the wizard panel werent setting up the setReuseItem in the
ListView It was hard to realize but I get it.
On Thu, May 14, 2009 at 9:17 PM, Jeremy Thomerson jer...@wickettraining.com
wrote:
Please file a
if you care to submit a quickstart that demonstrates this in a jira
issue im sure someone will fix it relatively quickly.
of course patches are applied even quicker :)
-igor
On Thu, May 14, 2009 at 4:02 PM, Fernando Wermus
fernando.wer...@gmail.com wrote:
Hi!,
I am facing a problem that I
Igor,
I can move to a newer wicket version. Do you know if this is a known
bug?
On Thu, May 14, 2009 at 4:05 PM, Igor Vaynberg igor.vaynb...@gmail.comwrote:
if you care to submit a quickstart that demonstrates this in a jira
issue im sure someone will fix it relatively quickly.
of
you can search jira for all known issues, i dont remember all of them
from the top of my head :)
-igor
On Thu, May 14, 2009 at 4:09 PM, Fernando Wermus
fernando.wer...@gmail.com wrote:
Igor,
I can move to a newer wicket version. Do you know if this is a known
bug?
On Thu, May 14, 2009
upgrading to a newer version is always preferred as a first measure.
Martijn
On Fri, May 15, 2009 at 1:12 AM, Igor Vaynberg igor.vaynb...@gmail.com wrote:
you can search jira for all known issues, i dont remember all of them
from the top of my head :)
-igor
On Thu, May 14, 2009 at 4:09 PM,
Hi all,
I moved to wicket 1.3.6, the lastest before 1.4, without any luck. What
I did next, it was to cut the code that was bother me and It is working now.
Of course, I am afraid that this could have colateral effects. This is the
code,
if (group.hasRawInput())
{
Please file a JIRA at the URL below [1]. The most effective issues
are ones that are submitted with a patch. To make it even more
effective, please run all tests against the patched codebase (run mvn
clean test) and notate that you did so when you submit your patch.
[1] -