anchor.diff:  	@Configuration
   	public class AppConfig {
   
  -		@Bean(name = { "dataSource", "subsystemA-dataSource", "subsystemB-dataSource" })
  +		@Bean({"dataSource", "subsystemA-dataSource", "subsystemB-dataSource"})
   		public DataSource dataSource() {
   			// instantiate, configure and return DataSource bean...
   		}
  
positive.code: Specifying all aliases where the bean is actually defined is not always adequate,
  however. It is sometimes desirable to introduce an alias for a bean that is defined
  elsewhere. This is commonly the case in large systems where configuration is split
  amongst each subsystem, with each subsystem having its own set of object definitions. In
  XML-based configuration metadata, you can use the `<alias/>` element to accomplish this.
  The following example shows how to do so:
  
  ====
  [source,xml,indent=0]
  
negative.code: In this case, a bean (in the same container) named `fromName` may also,
  after the use of this alias definition, be referred to as `toName`.
  
  For example, the configuration metadata for subsystem A may refer to a DataSource by the
  name of `subsystemA-dataSource`. The configuration metadata for subsystem B may refer to
  a DataSource by the name of `subsystemB-dataSource`. When composing the main application
  that uses both these subsystems, the main application refers to the DataSource by the
  name of `myApp-dataSource`. To have all three names refer to the same object, you can
  add the following alias definitions to the configuration metadata:
  
  ====
  [source,xml,indent=0]
  [subs="verbatim,quotes"]
  ----
  	<alias name="myApp-dataSource" alias="subsystemA-dataSource"/>
  	<alias name="myApp-dataSource" alias="subsystemB-dataSource"/>
  ----
  ====
  
  