This did it. Thank you very much.
Greg
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/force-model-update-on-a-wicket-form-tp4594765p4596253.html
Sent from the Users forum mailing list archive at Nabble.com.
Hi everybody.
First I would like to thanks you for the help you gave me.
But I've got another question for you.
I would like to know if it's possible to override the annotation @SpringBean
?
Why do I need to do that?
Let try a little simple example:
I want to print this
"Hello Internal"
and i
Hi,
in case like this where I would like to reuse a custom component in different
contexts, I
usually make the component abstract and have the using components implement an
abstract method such as "getService". This way, I can pass in different beans
as needed...
Maybe that helps,
Jürgen
On
Hi everyone.
I'm late out with migration. And I have a problem. We got a big system using
wicket.
The .xml change to .properties.xml could be painful. I could just rename all
xml files so I can reach the pages to check if some migration features has
been successful. But the check on the migration
You can use a custom IPropertiesFactory or adjust the default one, see
PropertiesFactory#getPropertiesLoaders().
Sven
On 04/30/2012 07:44 AM, jensiator wrote:
Hi everyone.
I'm late out with migration. And I have a problem. We got a big system using
wicket.
The .xml change to .properties.xml co