You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
collection elements in the beans schema (<list>, <set>, <map>, <props>, <array>) each expose a 'merge' attribute of type 'defaultable-boolean'. All such attributes should also explicitly set default="default", but these elements do not.
This violates expectations during parsing, as the parsing routine expects the default value to be the literal string "default", in which case the parent <beans> element's default values are interrogated as a fallback. Instead, these attributes default to empty string. Thus, if <beans default-merge="true"/> has been set, it never gets propagated to the individual collection elements, because the parsing routine didn't think it was necessary.
This appears to have been the case since as early as Spring 2.0. Apparently there aren't many folks using default-merge!
Chris Beams opened SPR-7656 and commented
collection elements in the beans schema (<list>, <set>, <map>, <props>, <array>) each expose a 'merge' attribute of type 'defaultable-boolean'. All such attributes should also explicitly set default="default", but these elements do not.
This violates expectations during parsing, as the parsing routine expects the default value to be the literal string "default", in which case the parent <beans> element's default values are interrogated as a fallback. Instead, these attributes default to empty string. Thus, if <beans default-merge="true"/> has been set, it never gets propagated to the individual collection elements, because the parsing routine didn't think it was necessary.
This appears to have been the case since as early as Spring 2.0. Apparently there aren't many folks using
default-merge
!Affects: 2.0 final
Referenced from: commits c7aaa85
The text was updated successfully, but these errors were encountered: