Update for "Spring Cloud Config Server and Legacy Spring Apps"

Hey, your article was a life-saver. Not sure how many people are left out there that want to enable Spring Cloud Config for a legacy app, but I sure will use it. I had a couple changes to the code if you're interested. I ditched the second class for the Environment and just included it inline:

@Override
protected ConfigurableEnvironment createEnvironment() {
    System.out.println("##################### loaded context");
    return new StandardServletEnvironment(){
        @Override
        protected void customizePropertySources(MutablePropertySources propertySources)
        {

I also put in a check to see if the PropertySource loaded correctly:

super.customizePropertySources(propertySources);
            try
            {
                PropertySource<?> source = initConfigServicePropertySourceLocator(this);
                if(source != null) {
                    propertySources.addLast(source);
                }
            }

I wanted to be able to use the bootstrap.properties like CloudConfigClient is supposed to when it starts up, so I changed:

private PropertySource<?> initConfigServicePropertySourceLocator(ConfigurableEnvironment environment)
            throws IOException {
            ClassPathResource resource = new ClassPathResource("bootstrap.properties");
            if(resource.exists()){
                Properties props = PropertiesLoaderUtils.loadProperties(resource);
                MutablePropertySources propertySources = environment.getPropertySources();
                propertySources
                    .addFirst(new PropertiesPropertySource("bootstrap", props));
            }
            LOGGER.info("*********  SASI LOADING CUSTOM **********");
            ConfigClientProperties configClientProperties = new ConfigClientProperties(environment);
            System.out.println(environment.toString());

            ConfigServicePropertySourceLocator configServicePropertySourceLocator = new ConfigServicePropertySourceLocator(configClientProperties);

to load bootstrap.properties if it exists, and add it as the first PropertySource. That way I can put spring.cloud.config.uri and spring.application.name in bootstrap.properties. Other than that, this was just what I needed. I went back and forth between trying to load my applicationConfig.xml from Spring, or loading Spring from the applicationConfig.xml.

I wanted to comment on the article, but the page won't reload once I log in. Thanks again.

sasiperi / sasiperi.github.io

Update for "Spring Cloud Config Server and Legacy Spring Apps" #6