How does the `@Value` annotation defining a default value interact with providing a default value in the initialization of the `emailAttributeName` member?  Will the `@Value` annotation always (when honored) replace the value of `emailAttributeName` set at declaration of `emailAttributeName`?  I suppose the default value in the variable declaration is doing work in setting a default value when the `@Value` annotation is not honored (say, outside the Spring container where a bean postprocessor would honor it?)   I'm surprised to see both setting defaults on member declaration and also setting defaults on `@Value` annotation?    But with that combination, shouldn't the default values declared in each match?