Versions Compared

Old Version 4

changes.mady.by.user Unknown User (m.woudstra)

Saved on

compared with

New Version 5

changes.mady.by.user Unknown User (m.woudstra)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

profile namecorresponding property file 
"dev"application-dev.properties 
"externaldatasources"application-externaldatasources.properties 
"jndidatasources"

application-jndidatasources.properties

 
"publisherclient"application-publlsherclient.properties 
"capture-http-session"application-capture-http-session.properties 
"single-session"application-single-session.properties 
"web-it"application-web-it.properties 
"widget-override"application-widget-override.properties 
"customer_a"application-customer_a.properties 
"customer_b"application-customer_b.properties 
"html-container"application-html-container.properties 
"vaadin-widget-engine"application-vaadin-widget-engine.properties 
   

 

 

bootstrap.properties

Spring provides a couple of ways to externalize application configuration. Blueriq makes use of the possibility to pick up application configuration from the classpath. To tell Spring to pick up configuration from the classpath we need to configure the bootstrap.properties as follows:

spring.cloud.config.server.bootstrap=true true

spring.profiles.active=native,dev

spring.cloud.config.server.native.searchLocations=file:${spring.config.location:.}