So I had a need to inject a custom validation message for a required text component when the field value is not present. No problem I said, looking at some wiki pages and other online content, I found that it should be easily added as any other i18n property: ..Required=My custom message.
Would it be true that the entire form id from the page level down is needed? tabs.panel. for instance? That seems to work. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Validation-messages-for-required-fields-using-form-id-tp3403212p3403612.html Sent from the Users
We have had to grab the beans ourselves for request scoped beans. In our case they are trying to cache service call results that may change over time and allows for data consistency through the request. If we use the @SpringBean annotation for this we have seen that the bean is cached and not
Again without seeing more of the code some of this is guessing. If the component that you are trying to update is not part of the original HTML it will not be updated in the ajax response. I see that you are marking the component as visible and enabled. If it isn't visible during the initial
Is there a best practice document or a set of examples that demonstrate a use of Wicket Channels. I have run into a couple places in an application where the service side of obtaining data might be costly. Using an AjaxLazyLoadingPanel and/or a LoadableDetachableModel has certainly helped, but