Can you show some code or (better) can you replicate your problem in a
quickstart application? In your opinion which are the behaviors in conflict?
For example, the Panel was showing/hiding some components inside itself,
based on the selection in those components; that was working correctly.
Right now, we're using the Panel on a separate page and have an external
component that needs to respond to the events in one of the Panel's
dropdowns. We don't want to change the Panel itself because it's a complex
reusable piece and we want to leave it alone. After adding an Ajax behavior
to that dropdown, it seems to run but overrides the previous behavior
defined for it.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Adding-to-the-existing-AjaxBehavior-of-a-component-tp4657400p4657412.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
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
