As we move away from the error bubbles, I think you'll see that errors will naturally attach to the fields, and <t:errors/> will just display errors not associated with a specific field.
On Fri, Apr 8, 2011 at 5:01 PM, Adam Zimowski <[email protected]> wrote: > By default BeanEditForm includes <t:errors/>. > > BeanEditor seems to expect that t:errors is placed outside if > programmer wants it. > > Intuitively, I would expect a feature for both to support inline errors: > > <t:beaneditform inlineErrors="literal:true" /> > <t:beaneditor inlineErrors="literal:true" /> > > with <t:error> rendered next to a field and some CSS class to override. > > That would be nice. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
