Why don't you submit a "wish" jira for the functionality, sounds like something that makes sense to develop.
On 9/4/07, Stephen Friedrich <[EMAIL PROTECTED]> wrote: > Andrew Robinson wrote: > > No, it requires a "for" attribute. That is the component that the > > label and the message are for. Also in 1.0.3 the code will > > automatically use the first EditableValueHolder it finds if the for is > > not given, but it still only supports one component. To get multiple > > components, you have to have multiple panelLabelAndMessage components. > Hm, that kind of defeats the purpose of panelLabelAndMessage: > I nested firstName and lastName fields in a single panelLabelAndMessage > to have them shown in a single row of a form managed by panelFormLayout. > Of course I'd like to show messages for both of them. > How can I do that? > Can I switch the automatic message part OFF and then add two tr:message > tag (one for each input field)? Then again that would require some > additional layout to get the messages to appear under the correct field. > > It really would be easiest to be able to have a "semi-simple" where the > component does not manage its label, but manages its own message. > simple="message-only" ? > > BTW: The same structure repeats in my app with other pairs with other > pairs (zip/city, start/end date, street/no, ...). > >
