Ted, Thanks for the feedback. Can you clarify the following two details? Regarding the rest of your mail I'll follow up.
Ted Husted wrote: [...] > The ActionMessages are basically an enhanced version of ActionErrors. It > acts like an iterator, rather than just spitting everything out. We kept > the ActionErrors mostly for backward compatability. It also lets > developers send confirmations through one queue, and "errors" through > another. But I generally just use one or the other myself. So, we should really provide a set of methods similar to what we offer for handling errors? public boolean hasMessages(); public int messageSize(); public int messageSize(String property); public HashMap messages(); public HashMap messages(String property); public String messageMarkup(String header, String footer); public String messageMarkup(String property, String header, String footer); (We need to rething the naming once we know what tools there will be.) Regarding the transaction tag, my understanding is that it is something that should really be dealt with in the Action and therefore we don't need methods to handle this in the template. Is that right? Gabe -- Gabriel Sidler Software Engineer, Eivycom GmbH, Zurich, Switzerland -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
