[bs-73] Tweak configuration class detection algorithm some more

This looks like becoming a recurring theme. Unfortunately it's
not very easy to test if a class might eventually be instantiatable
by Spring.

This change fixes the main bootstrap SpringApplicationTests
which were failing because they used non-static inner classes
for test configurations.
This commit is contained in:
Dave Syer
2013-04-26 10:39:06 +01:00
parent d6a670e13e
commit 4ca26058fa
2 changed files with 7 additions and 2 deletions

View File

@@ -24,7 +24,6 @@ import org.springframework.beans.BeansException;
import org.springframework.beans.factory.support.BeanDefinitionRegistry;
import org.springframework.beans.factory.support.BeanNameGenerator;
import org.springframework.beans.factory.support.DefaultBeanNameGenerator;
import org.springframework.bootstrap.context.annotation.EnableAutoConfiguration;
import org.springframework.bootstrap.context.embedded.AnnotationConfigEmbeddedWebApplicationContext;
import org.springframework.bootstrap.context.embedded.jetty.JettyEmbeddedServletContainerFactory;
import org.springframework.context.ApplicationContext;
@@ -331,7 +330,6 @@ public class SpringApplicationTests {
}
@Configuration
@EnableAutoConfiguration
static class ExampleWebConfig {
@Bean