That's certainly true, but there does exist a default filter configured with previous behavior. If you would review the file `RegisteredServiceDefaultAttributeFilter`, that's where the default behavior is encapsulated which is effectively and exactly what happens now. The spring configuration then registers that filter into the chain and that configuration is also provided in the `deployerConfigContext.xml` file.