properties-file

I work on a java project where labels are externalized and translated into .properties files. Resources in java are read using ISO-8859-1 encoding and thus the .properties files are also stored in ISO-8859-1 encoding. The current files are messed up, sometimes using escapes \u00E4 and sometimes using the actual letter öäü . Also I have russian translations which look like this: code.adr=\u0430\u0434\u0440\u0435\u0441 This could be stored in clear text using UTF-8. Now the question is, why not use UTF-8? Why does Java use ISO-8859-1 instead of UTF-8 per default, backwards compability? Are there

I have built a spring boot project. Within it, I have a properties class that looks like this: @Configuration @PropertySource(value = "classpath:abc.properties") @ConfigurationProperties public class ABCProperties { private Map<String, String> someUrls; @Bean public Map<String, String> someUrls() { return someUrls; } public Map<String, String> getSomeUrls() { return someUrls; } public void setSomeUrls(Map<String, String> someUrls) { this.someUrls = someUrls; } } The contents of the abc.properties file look like this: someUrls.urlA=someURL someUrls.urlB=someOtherURL Within the project, in the

I was wondering how to use an external file to load some properties for my app in different contexts.. I know I can pass a file in PropertySource annotation. The problem is the path of the file. I mean, it looks like it want a full path to the file, but different environments have different paths for Tomcat directory. My question is: Where is the correct directory to store this files (it must be outside to the app dir otherwise on every deploy it is deleted) and how I can link it in my application. For instance, now i created a /config directory inside the /webapps directory of tomcat. From my

I have been tasked with an assignement at work, that needs persistance of client side settings. These settings are represented by a XML-file in the C# version of the framework I am implementing, and it represents objects with an hierarchical structure of up to six levels. Also, the number of objects in the different levels are sometimes arbitrary, like an ArrayList. Object serialization is unfortunately not an option, due to a requirement of being able to edit the file directly. It has been more than implied that I have to implement the persistance of these settings as a .properties-file, but

I'm currently building a RESTful API using Jersey. So far, all has been going well, however, all of the configuration entries have been hard coded in. (i.e. Database Host , Database Username , etc...). I'd like to be able to setup a config.properties file that exists in my WEB-INF folder to contain all of these configuration specs. I'm concerned that if I do it the "classic" way of reading the file on the Classpath, I'm performing file I/O for every request. I want to be able to read once on startup (which I know involves a ServletListener in my web.xml file. Here's what I have below: web.xml

I'm translating a Java application by using a ResourceBundle with various *.properties files. Now I like to have a Gradle task or want to modify a task to automatically escape any unicode character by replacing it with its ASCII representation, something like Java's native2ascii tool does. This is what I'm done so far with my build file, but the output remains unescaped : import org.apache.tools.ant.filters.EscapeUnicode tasks.withType(ProcessResources) { filesMatching('**/*.properties') { println "\t-> ${it}" filter EscapeUnicode } } Any help is appreciated. You can do it providing the

I've generated a Spring Boot web application using Spring Initializr, using embedded Tomcat + Thymeleaf template engine. I put this property in my application.properties default.to.address=nunito.calzada@gmail.com I am using Spring Tool Suite Version: 3.8.4.RELEASE as a development environment, but I got this warning in the Editor 'default.to.address' is an unknown property. Should I put this property in another property file ? It's because it's being opened by the STS properties editor which validates properties amongst other things. There's no harm in having it in the application.properties