This sounds very strange. If you disable a component the model value will still be rendered to the html. disabled is used differently by different component components, for example a disabled textfield will add a disabled attribute to the html output but a disabled link will replace the tag with a span so the link won't be clickable.
Can you show us some code? Maurice On Fri, May 23, 2008 at 10:17 PM, alesp <[EMAIL PROTECTED]> wrote: > > Hi, this is my problem: I have a form and 2 date fields. When the form is > submitted for the first time, I do some validation on those fields and if > everything goes ok, then I store the model object. Eventually, I have to > disable the first of the 2 date fields to prevent modification, but the > second one still needs to be editable. The thing is that when I do that, > when I disable the first of the datefields I get a nullPointerException in > the validator because I receive a null DateTime instead a date for the > disabled field. > If I setenabled(false) in a component then the content is not submitted? How > can I do to still validate the date interval if I'm getting only the enabled > date? > -- > View this message in context: > http://www.nabble.com/Problems-disabling-componets-and-submitting-them-to-validation-tp17440116p17440116.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
