properties-file

We are loading properties from an external file using @PropertySources . Now I want to enable/disable @Aspect based on a property. I tried using @ConditionalOnExpression which didn't work. I tried the same by creating a bean of propertyplaceholderconfig . Even in the same case, it didn't work. Then I tried @profile which also didn't work initially. What I Figured out is that these variables are not initialized at the starting when propertysource or propertyplaceholder bean is used at startup. Some variables are always ignored like (logging.file). But @Value works fine. In order to set these

I am trying to find a way to set UTF-8 encoding for properties accessed via @Value annotation from application.property files in Spring boot. So far I have been successfully set encoding to my own properties sources by creating a bean: @Bean @Primary public PropertySourcesPlaceholderConfigurer placeholderConfigurer(){ PropertySourcesPlaceholderConfigurer configurer = new PropertySourcesPlaceholderConfigurer(); configurer.setLocation(new ClassPathResource("app.properties"); configurer.setFileEncoding("UTF-8"); return configurer; } Such solution presents two problems. For once, it does NOT work

Is it possible, in a JSF page, to show a property loaded from a project.properties file (for example the database name)? In project.properties : cfg.bd.dbname=midatabase-name In some jsf page some expression similar to this: <h:outputText value="#{cfg.bd.dbname}" /> Thanks! You can (ab)use <f:loadBundle> for this. <f:loadBundle basename="project" var="project" /> ... <h:outputText value="#{project['cfg.bd.dbname']} /> I said abuse , because the <f:loadBundle> is initially intented to load localized text bundles which allows for internationalization, but as it's under the covers using the same

I'm using MessageSource of Spring to load errors messages from a .properties file in classpath. My properties respect a certain "template" such as {Object}.{field}.{unrespectedConstraint} Example : userRegistrationDto.password.Size= Le mot de passe doit avoir au minimum 6 caractères. userRegistrationDto.email.ValidEmail= Merci de saisir une addresse mail valide. In case of refactoring (Changing the name of the class for example), I have to change my properties file in several places. Is there any way to use a yaml file (messages.yml) as a ResourceBundle to obtain something like :

I know this question has answered many a time with most useful answer as below, Where to place and how to read configuration resource files in servlet based application? However, We have some special requirement as below, Webapp will be deployed to tomcat. Normal java app in form of .jar will be placed under folder /myapp myappConfig.property file will be placed under /myapp Directory Structure on client machine /myapp /myapp.jar /assests/myappConfig.property /tomcat/webapps/myapp.war Basically myapp.jar and myapp.war will access sql db connection values for MySql database connection and db

is it possible to add to the classpath of a runnable jar file some properties file? I tryed these solutions solutions: running the executable file using the following command: java -cp ../prop_dir/prop1.properties;../prop_dir/prop2.properties -jar MyRunnableJar.jar adding to the MANIFEST FILE (in the Class-Path section) ../prop_dir/prop1.properties ../prop_dir/prop1.properties but none of them works. The architecture of the running dir is the following + + MyRunnableJar.jar + prop_dir/ + prop1.properties + prop2.properties Thanks so much, Daniele EDIT When I execute the following line System

I was trying to define the cron details in my spring @Scheduled method @Service @PropertySource("classpath:application.properties") public class CacheRefreshService { @Scheduled(cron = "${api.refresh.cron}") public void refreshJob() throws Exception { LOGGER.info("Started Refresh"); //do something } } And in my application.properties #Refresh api.refresh.cron =0 29 11 * * ? When I define the cron details along with @Scheduled, it is running fine. But when I do this, it is not able to read the value from the properties file and the below error is thrown. Caused by: java.lang