Hi David,
With the event mechanism, you don't need to keep reference.
Yours components keep loosely coupled.
In the onPageChanged() method you can send an event like this
send(getPage(), Broadcast.BREADTH, new YourEvent());
see the exemple: http://www.wicket-library.com/wicket-examples/events/
ORACLEADF wrote:
Hi Nick
Thank you.
I create a file applicationContext.xml like the following pic and I use it
in DAO and BO classes :
Is your applicationContext.xml read at all?
I.e., are your beans actually created?
To check: Does your log contains a line like
INFO XmlBeanDefinitionReader
OK, your test doesnt test anything Wicket related, and is purely a Spring
application.
In order to use Spring in a wicket app, you need to check out some of the
articles on the web - Google for Wicket spring application and there are
several full working examples of how to use Spring in a Wicket
Hi Francois
Thanks for your help, this useful in firing the event but how can I get
it so that the buttons state is updated on the page. Sorry If I am
missing something but am having trouble seeing how I can do this if I
can't get hold of the AjaxRequestTarget.
I am using wicket 6.6.0
Hi Francois
Thanks for the pointers I have now solved this problem thanks again.
David
On 12/05/13 18:38, David Beer wrote:
Hi Francois
Thanks for your help, this useful in firing the event but how can I
get it so that the buttons state is updated on the page. Sorry If I am
missing
