SEC-1029: Namespace configured beans cannot be used for autowiring #1281

Closed
spring-issuemaster opened this Issue Nov 10, 2008 · 1 comment

1 participant

@spring-issuemaster

Joonas Koivunen (Migrated from SEC-1029) said:

Many namespace configurable elements lack “alias” property. Better than to add aliases to everything would be publish all beans as normal beans available for autowiring.

For example:

There’s no way to “recover” in the example below:

Otherwise it would be great if userManagementServices would be automatically proxied to get encoded passwords to changePassword(…) method, currently it is very difficult to provide custom userManagementService that encodes passwords the same way as authentication service encodes those.

@spring-issuemaster

Luke Taylor said:

This isn’t a bug. The namespace is intended to provide a simplified configuration syntax for users who do not need the flexibility of configuring the beans directly. Thus it deliberately hides bean implementations (except in a few specific cases). You have other customisation options such as using traditional bean configurations for the AuthenticationProvider and linking this into the namespace.

@spring-issuemaster spring-issuemaster added this to the 3.0.0 M1 milestone Feb 5, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment