Re: Validation messages for required fields using form id

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

Validation messages for required fields using form id

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. However

Re: spring bean null during ajax call back

Here are a couple threads that back this and provide links to more deeper explanations of the annotation. http://apache-wicket.1842946.n4.nabble.com/Hold-a-reference-to-a-Spring-bean-in-Wicket-components-td1880461.html http://apache-wicket.1842946.n4.nabble.com/wicket-serlization-impact-on-singl

Re: spring bean null during ajax call back

The fact that the bean is declared transient means that when the component is serialized the field will be nulled out. The @SpringBean annotation actually proxies the actual spring bean for you with it's own serializable instance that (a) is serializable and (b) simply knows how to look the bean u

Re: Bean injection

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 "ref

Re: Model Is Not being Refreshed

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 re

Wicket Channels best practices

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 we'