anchor.diff:  	}
   ----
   
  +[NOTE]
  +====
  +As mentioned before, with `@Bean` methods, you will typically choose to use programmatic
  +JNDI lookups: either using Spring's `JndiTemplate`/`JndiLocatorDelegate` helpers or the
  +straight JNDI `InitialContext` usage shown above, but not the `JndiObjectFactoryBean`
  +variant which would force you to declare the return type as the `FactoryBean` type.
  +====
   
   `@Profile` can be used as a <<beans-meta-annotations,meta-annotation>> for the purpose
   of creating a custom _composed annotation_. The following example defines a custom
  
positive.code: 	}
  ----
  
  ====
  
  Of course, in the case of `Foo` above, it would be equally as valid to call the `init()`
  
negative.code: shuts down, simply 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 via JNDI as its
  lifecycle is managed outside the application. In particular, make sure to always do it
  for a `DataSource` as it is known to be problematic on Java EE application servers.
  
  [source,java,indent=0]
  [subs="verbatim,quotes"]
  