DefaultOptions resolver does not create a new CL

- This will make sure the options metadata classes are loaded from the jars provided in the current classloader instead of a new ParentLastURLClassLoader created in XD.
This commit is contained in:
Ilayaperumal Gopinathan
2015-06-17 12:16:43 -07:00
committed by Mark Fisher
parent 6ab7c566ad
commit 71e53321dc
2 changed files with 5 additions and 3 deletions

View File

@@ -12,9 +12,9 @@
</organization>
<properties>
<java.version>1.7</java.version>
<spring-boot.version>1.3.0.BUILD-SNAPSHOT</spring-boot.version>
<spring-boot.version>1.3.0.M1</spring-boot.version>
<spring-cloud.version>1.0.3.BUILD-SNAPSHOT</spring-cloud.version>
<spring-xd.version>1.2.0.BUILD-SNAPSHOT</spring-xd.version>
<spring-xd.version>2.0.0.BUILD-SNAPSHOT</spring-xd.version>
</properties>
<modules>
<module>spring-bus-core</module>

View File

@@ -105,7 +105,9 @@ public class ModuleOptionsPropertySourceInitializer implements
@Bean
// TODO: allow override of this
public DefaultModuleOptionsMetadataResolver defaultResolver() {
return new DefaultModuleOptionsMetadataResolver();
DefaultModuleOptionsMetadataResolver defaultResolver = new DefaultModuleOptionsMetadataResolver();
defaultResolver.setShouldCreateModuleClassLoader(false);
return defaultResolver;
}
@ConditionalOnExpression("'${xd.module.config.location:${xd.config.home:}}'!=''")