On Jan 16, 2008 1:47 PM, Jared Rypka-Hauer <[EMAIL PROTECTED]> wrote: > Dave, I talked to you about this last night. Brian Kotek helped me find the > fix... I implemented and committed. > > I had to add "no" to the list of bean tag autowiring overrides because it > only recognized byName and byType... so you couldn't shut autowiring off for > a particular bean. > > Very bad if you had a setter (say... setFoo()) and a bean (say id="foo") > with matching names but you didn't ACTUALLY want it injected. It's fixed, > and tested.
I'm puzzled. The Spring DTD says that the overall default autowire should be "no" (<beans default-autowire="no">) and that for each bean it should be "default" (<bean autowire="default">). Are you saying that the default autowire is *not* "no"? Is that a known, intentional decision to vary from Spring? Of course, "no" is supposed to be accepted for both default-autowire on beans and autowire on bean per the DTD so it definitely needed to be added. It just sounds like there's a deeper issue in terms of defaults... -- Sean A Corfield -- (904) 302-SEAN An Architect's View -- http://corfield.org/ "If you're not annoying somebody, you're not really alive." -- Margaret Atwood
