anchor.diff:  	@Profile("production")
   	public class JndiDataConfig {
   
  -		@Bean(destroyMethod="")
  +		@Bean(destroyMethod = "") // <1>
   		public DataSource dataSource() throws Exception {
   			Context ctx = new InitialContext();
   			return (DataSource) ctx.lookup("java:comp/env/jdbc/datasource");
   		}
   	}
   ----
  +<1> `@Bean(destroyMethod = "")` disables default destroy method inference.
  +
   [source,kotlin,indent=0,subs="verbatim,quotes",role="secondary"]
   .Kotlin
   ----
  
positive.code: By default, beans defined with Java configuration that have a public `close` or `shutdown`
  method are automatically enlisted with a destruction callback. If you have a public
  `close` or `shutdown` method and you do not wish for it to be called when the container
  shuts down, you can add `@Bean(destroyMethod="")` to your bean definition to disable the
  default `(inferred)` mode.
  
  You may want to do that by default for a resource that you acquire with JNDI, as its
  
negative.code: expressed (for example, `production & us-east`). The following operators are supported in
  profile expressions:
  
  * `!`: A logical `NOT` of the profile
  * `&`: A logical `AND` of the profiles
  * `|`: A logical `OR` of the profiles
  
  NOTE: You cannot mix the `&` and `|` operators without using parentheses. For example,
  `production & us-east | eu-central` is not a valid expression. It must be expressed as
  