I tend to agree with you Martin and understand that 1.0.1 is intended to be a bug fix branch only. I'll post a 1.1 patch soon.
As far as the implementation goes, you are correct in assuming that it is "last one in wins". This follows the current implementation of how duplicate elements are handled. For instance if I were to declare 2 forwards with the same name the "last one wins". I presumed this was accepted behavior based off of the fact that it already happens this way, but I can certainly put together a revised patch that logs duplicates. What do others think should happen? I am personally on the fence and will be happy to submit a new patch with the desired functionality. -james [EMAIL PROTECTED] http://www.ejcenter.com/struts/ --- [EMAIL PROTECTED] wrote: > I don't know how other people feel, but personally, > I see this as new > functionality, rather than a bug fix. Hence I'd be > happy to see this added > for Struts 1.1, but I'd be reluctant to see it added > for the Struts 1.0.1 > patch. > > Incidentally, I assume this implementation is > effectively "last one in > wins". That is, if I have form beans (or action > mappings, etc.) with the > same name in multiple config files, the last one > read is the one that will > actually be used. If that's the case, it might be > useful, for debugging > purposes, to log a message when one entry is > overwritten by a later one. > > -- > Martin Cooper __________________________________________________ Do You Yahoo!? Make a great connection at Yahoo! Personals. http://personals.yahoo.com
