[
https://issues.apache.org/jira/browse/WICKET-3903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carl-Eric Menzel updated WICKET-3903:
-------------------------------------
Attachment: 0001-port-AutoLabelTextResolver-from-1.4.patch
Based on Igor's improvements, I ported the whole thing up to trunk (1.5).
I resurrected ResponseBufferZone that was deleted in 1.5 a while ago. Enclosure
doesn't use it anymore, but it is quite handy for AutoLabelTextResolver (and I
think some other places that push StringResponse around manually could benefit
from this too).
> Split AutoLabelResolver into wicket:for and wicket:label
> --------------------------------------------------------
>
> Key: WICKET-3903
> URL: https://issues.apache.org/jira/browse/WICKET-3903
> Project: Wicket
> Issue Type: Improvement
> Components: wicket-core
> Affects Versions: 1.4.18, 1.5-RC6
> Reporter: Carl-Eric Menzel
> Assignee: Igor Vaynberg
> Attachments: 0001-port-AutoLabelTextResolver-from-1.4.patch,
> 0001-split-autolabelresolver.patch, WICKET-3903.diff
>
>
> AutoLabelResolver is combining two different things - managing the "for"
> attribute in <label>, and managing FormComponent#getLabel.
> After an IRC conversation with martin-g and ivaynberg, I propose splitting
> this behavior into two parts, as done in the upcoming patch. Use wicket:for
> as before, use <wicket:label> to output or pick up the label string. See
> AutoFormComponentLabelResolver for details.
> AutoLabelResolver also did not play nice with Enclosure - it would confuse
> Enclosure and make it throw ArrayIndexOutOfBoundExceptions. That could be
> cured by having AutoLabelTagResolver do setAutoComponentTag=true, but that
> again would break AutoLabelResolver's <span> magic. By splitting it up like
> this, that issue is avoided, and wicket:for, wicket:label and Enclosure play
> nicely together.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
