Hi Andrea,
this is the code (a bit pseudo-like...) I am quite sure it is not the
way it should be and full of wicket anti-patterns. But still exists
since my first wicket experiences 2 years ago. ;-)
This panel gets rendered via RefreshingView about 30 times.
public ElementPanel(String id,
I think you might have over-complicated your design.
Yes, I also think so, but unfortunately currently I'm not able to
redesign it, and I try to find a quick solution. :-/
(please have a look at my reply to andreas mail. There is some code...)
should be simple to update the parent which in
I just wanted to report back and say that, after our installer team
updated the distribution to maintain the individual JARs (and thus not
overwrite the files with clashing filenames), that solved the problem!
Thanks to Martin Grigorov and Andrew Geery for helping point me in the
direction of
On 08/20/2014 10:08 AM, Shawn McKinney wrote:
Notably missing from the material is theory or why these types of
complex security mechanisms are necessary. I'm working on that now and
will publish it back here when ready.
Hello again, just now getting back to this thread
***
The
Thankyou very much for yours reply.
I call formComponent.clearInput() in my ClearFormVisitor class. But It does
not work.
I have created issue-96
https://github.com/ivaynberg/wicket-select2/issues/96 in wicket-select2
project.
On Wed, Oct 8, 2014 at 12:13 AM, Maxim Solodovnik
I also noticed this issue in our project,
Will try to take a look at it
On 9 October 2014 07:33, MadasamySankarapandian madas...@mcruncher.com
wrote:
Thankyou very much for yours reply.
I call formComponent.clearInput() in my ClearFormVisitor class. But It does
not work.
I have created
