Cause Im eager to learn new things :)
Regards, Satrix
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Wicket-1-5-8-EJB-3-1-strange-problem-tp4653977p4654128.html
Sent from the Users forum mailing list archive at Nabble.com.
Chris
Ive been following this thread with interest - what is the use case that
drives your need to add components dynamically - why can't you just add a
SytemPanel in the panel constructor - is your HTML markup being generated
outside of your Wicket app?
N
On Nov 24, 2012 1:26 AM, Chris Colman
Good evening,
Let me reply to myself, please ! :-)
I've found the solution. The exception came from the fact that my
@Subscribe-annotated method responsible of adding the component to the
target was using a filter predicate. Remove that and it works!
Hope that could help someone in the future.
What is the problem?
Sven
On 11/24/2012 08:22 PM, Oliver Zemann wrote:
Hi,
i created a small wicket application to show my problem:
https://github.com/olze/WicketPanelReplace
The first panel gets displayed, after a few seconds it should be
replaced by the second panel. Is there any way to
The problem is that this leads to a Page not found error. The problem is
that the Panel which should be replaced is still looked up in the
findPage() method. But findPage() returns null on that component, so
this error is thrown.
Am 24.11.2012 21:48, schrieb Sven Meier:
What is the problem?
After the timer has fired, AbstractAjaxTimerBehavior automatically
registers another timeout for the form inside PanelOne.
But at that point PanelOne is no longer in the component tree, it's
replaced by PanelTwo already.
I'd recommend adding the behavor to the container instead:
final
Unfortunately this is not a solution as i have about 30 different
panels. And i guess at least 10 of them should later use JS. With the
approach you suggested i would have to check which panel should be
displayed and load that (switch/case with 10 different panels). I guess
that would also
Chris
Ive been following this thread with interest - what is the use case
that
drives your need to add components dynamically - why can't you just add
a
SytemPanel in the panel constructor - is your HTML markup being
generated
outside of your Wicket app?
Our use case is as follows:
We have a
just checked in a first pass on bean validation (jsr 303) integration.
see this commit for details:
https://git-wip-us.apache.org/repos/asf?p=wicket.git;a=commitdiff;h=580a8dd9;hp=2d47bf340875f6053aa2a3b69c4f442f2fbb03e1
feedback is welome.
-igor
