Hi Christophe! Regarding (1): it sounds like you are not using models properly; Models are what makes a component “dynamic” - they pull data from a source (which could be a static string). Can you show us some code?
Regarding (2): Can you show us the exceptions you get? In any case you should be aware that you cannot re-render a hidden component, unless you set its setOutputMarkupPlaceholderTag(true) method, ensuring that there is always a HTML element to replace. Another common solution is to re-render a container element which is always present in the HTML. Met vriendelijke groet, Kind regards, Bas Gooren Op 4 januari 2017 bij 14:33:34, christophe (madeleine.christo...@wanadoo.fr) schreef: Hello dear readers I am working on a web application that is very very AJAX-oriented. In other words any "displayed" page gets updated many times as a consequence of events such as (html) blur, mouse click. By updating I mean One or more fields become visible or invisible One or more fields become enabled or disabled Their content (for example a drop down list) changes Many more To actually "change" a markup component I 1) create a new one and replace the existing one or udpate the Component (for example to enable it) 2) Add this component to the AjaxRequestTarget I must do both because if I do 1 only: the change is not reflected in the web page. 2 only the component is not in the right "state" and I get all sorts of exceptions when it receives a message So I was wondering 1) AM i doing this right or amm I missing the obvious 2) If I am not doing anything wrong would it be possible to "enhance" Wicket so that any replace or "state", content update gets added "automatically" to the Request Target? I sincerely hope to hear from someone. Christophe -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Question-Suggestion-about-updating-a-component-in-aw-existing-page-Wicket-6-x-tp4676637.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
