Hi,
Thank you for the solution ; Yes, I fixed it by using
IComponentInitializationListener & IDetachListener.
Regards,
Rakesh.A
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Alternatives-for-Page-componentChanged-Component-MarkupContainer-Wicket-6-5-0-tp4659644p4
Hi,
You can use org.apache.wicket.application.IComponentInitializationListener.
See org.apache.wicket.Application#getComponentInitializationListeners().add(..)
On Mon, Jul 1, 2013 at 8:04 AM, Rakesh A wrote:
> Hi,
>
> In 1.4.x implementation, we were overriding this method [int our base Page
>
Hi,
In 1.4.x implementation, we were overriding this method [int our base Page
implementation] and were doing bit of initialization for the components of
the page which is [I mean initialization part - UI related] specific to our
implementation.
This was one central location to do this for any co
I'm not sure I understand your question.
All that method does is to set the dirty flag on the Page so a new instance
of the page would end up in your page store if any component on the page
changed.
What are you trying to do?
On Tue, Jun 25, 2013 at 12:36 AM, Rakesh A wrote:
> Hi,
>
> Is ther
Hi,
Is there any other way for the mentioned method?
Any suggestions?
Regards,
Rakesh.A
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Alternatives-for-Page-componentChanged-Component-MarkupContainer-Wicket-6-5-0-tp4659644p4659763.html
Sent from the Users forum ma
Hi,
Page.componentRemoved(Component) && Page.componentAdded(Component) are final
methods, I can not override them in my Page implementation.
Regards,
Rakesh.A
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Alternatives-for-Page-componentChanged-Component-MarkupCon
On Fri, Jun 21, 2013 at 9:57 AM, Rakesh A wrote:
> Hi,
>
> May be I should've added more details to my question.
> Code recently upgraded from v1.4.21 to v6.5.0. Old implementation code we
> are using this method to do some initialization whenever a component gets
> added/removed.
>
You can use o
Hi,
May be I should've added more details to my question.
Code recently upgraded from v1.4.21 to v6.5.0. Old implementation code we
are using this method to do some initialization whenever a component gets
added/removed.
As this method is not being called anymore, the initialization code is not
g
Hi,
>From your other question today I have the feeling that you still use Wicket
1.4.
In which case this method is called in 1.4 and not called in 6.x ?
On Fri, Jun 21, 2013 at 8:09 AM, iamrakesh wrote:
> Hi,
>
> In Wicket 1.4.x org.apache.wicket.Page.componentChanged(Component,
> MarkupContai
