On Mon, 16 Jul 2001, Ted Husted wrote:
> +1 for 1.1
>
> Following "The Principle of Least Astonishment", I'd say developers
> would expect the errors to be first-in first-out, and most are surprised
> when they see they are not (heck, it still surprises me!); the overhead
> seems worthwhile.
>
HashMaps ... gotta love 'em. :-)
> I would say it should be the default behavior in 1.1, and that an option
> seems unnecesssary.
>
+1.
Craig
> David Winterfeldt wrote:
> >
> > I think it would be good if the initial order a
> > property/key that is added to
> > ActionMessages/ActionErrors is maintained, but I
> > wondered what others think. I think it is easier to
> > read the error messages on the web page if they match
> > the order of the fields on the page. I have some code
> > written to maintain the order and I wondered if it
> > should default to this behavior which would be a
> > little more overhead generating the Iterator or if it
> > should be an option (like setSorted(boolean).
>
