Thanks for the explanation, Ted. So, it would be correct to say that an 'errorOutput' method of sorts must remain in the ConfigHelper API, but would be extraneous in the Velocity/Struts API, right?
> Nathan Bubna wrote: > > either way, the more i think about it, the more i think this whole > > 'errorMarkup' idea is rendered completely unnecessary by Velocity. or am i > > missing something? > > It relates to how the errors tag works in 1.0. There was just one tag > > <html:errors/> > > that could do all the work. > > In 1.1, there's a message tag that works more like you would expect. > > The Struts API bean would need to keep this method for backward > compatability. > > My goal is to be able to have the Struts custom tags use the same API > that we expect other presention layers to use. Sadly, not every > presentation layer is as capable as Velocity :o) > > > -- Ted Husted, Husted dot Com, Fairport NY USA. > -- Java Web Development with Struts. > -- Tel +1 585 737-3463. > -- Web http://www.husted.com/struts/ > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
