Re: Alternatives for Page.componentChanged(Component, MarkupContainer) - Wicket 6.5.0

2013-07-02 Thread Rakesh A
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-tp4659644p4659957.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: Alternatives for Page.componentChanged(Component, MarkupContainer) - Wicket 6.5.0

2013-07-01 Thread Martin Grigorov
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 iamrakes...@rediffmail.com wrote:

 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 component change on the
 page with v1.4.x, as we upgraded Wicket libarary to 6.5.0 recently, we're
 looking for alternatives for this method.

 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-tp4659644p4659932.html
 Sent from the Users forum mailing list archive at Nabble.com.

 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org




Re: Alternatives for Page.componentChanged(Component, MarkupContainer) - Wicket 6.5.0

2013-06-30 Thread Rakesh A
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 component change on the
page with v1.4.x, as we upgraded Wicket libarary to 6.5.0 recently, we're
looking for alternatives for this method.

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-tp4659644p4659932.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: Alternatives for Page.componentChanged(Component, MarkupContainer) - Wicket 6.5.0

2013-06-26 Thread Paul Bors
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 iamrakes...@rediffmail.comwrote:

 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 mailing list archive at Nabble.com.

 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org




Re: Alternatives for Page.componentChanged(Component, MarkupContainer) - Wicket 6.5.0

2013-06-24 Thread Rakesh A
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 mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Alternatives for Page.componentChanged(Component, MarkupContainer) - Wicket 6.5.0

2013-06-21 Thread iamrakesh
Hi,

In Wicket 1.4.x org.apache.wicket.Page.componentChanged(Component,
MarkupContainer) is called every time a component gets changed, it seems it
is not being called anymore in wicket 6.5.0.

Is there any alternative for this method?
Is there any way to listen for event when a component is
add/changed/removed/repalced to/from a page?

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-tp4659644.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: Alternatives for Page.componentChanged(Component, MarkupContainer) - Wicket 6.5.0

2013-06-21 Thread Martin Grigorov
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 iamrakes...@rediffmail.comwrote:

 Hi,

 In Wicket 1.4.x org.apache.wicket.Page.componentChanged(Component,
 MarkupContainer) is called every time a component gets changed, it seems it
 is not being called anymore in wicket 6.5.0.

 Is there any alternative for this method?
 Is there any way to listen for event when a component is
 add/changed/removed/repalced to/from a page?

 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-tp4659644.html
 Sent from the Users forum mailing list archive at Nabble.com.

 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org




Re: Alternatives for Page.componentChanged(Component, MarkupContainer) - Wicket 6.5.0

2013-06-21 Thread Rakesh A
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
getting executed anymore [with v6.5.0].

I am looking for alternatives for this method in new v6.5.0 api.

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-tp4659644p4659653.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: Alternatives for Page.componentChanged(Component, MarkupContainer) - Wicket 6.5.0

2013-06-21 Thread Martin Grigorov
On Fri, Jun 21, 2013 at 9:57 AM, Rakesh A iamrakes...@rediffmail.comwrote:

 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 org.apache.wicket.Page#componentRemoved()
and org.apache.wicket.Page#componentAdded() instead.



 As this method is not being called anymore, the initialization code is not
 getting executed anymore [with v6.5.0].

 I am looking for alternatives for this method in new v6.5.0 api.

 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-tp4659644p4659653.html
 Sent from the Users forum mailing list archive at Nabble.com.

 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org




Re: Alternatives for Page.componentChanged(Component, MarkupContainer) - Wicket 6.5.0

2013-06-21 Thread Rakesh A
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-MarkupContainer-Wicket-6-5-0-tp4659644p4659655.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org