As per “The New Idiot’s” suggestion, this stores in alphabetical key order. Properties tmp = new Properties() { @Override public synchronized Enumeration<Object> keys() { return Collections.enumeration(new TreeSet<Object>(super.keySet())); } }; tmp.putAll(properties); tmp.store(new FileWriter(file), null);
You can use ConvertFrom-StringData to convert Key=Value pairs to a hash table: $filedata = @’ app.name=Test App app.version=1.2 ‘@ $filedata | set-content appdata.txt $AppProps = convertfrom-stringdata (get-content ./appdata.txt -raw) $AppProps Name Value —- —– app.version 1.2 app.name Test App $AppProps.’app.version’ 1.2
If all lines in the input file are of this format, then simply sourcing it will set the variables: source nameOfFileWithKeyValuePairs or . nameOfFileWithKeyValuePairs
Root cause: By default ISO 8859-1 character encoding is used for Eclipse properties file (read here), so if the file contains any character beyond ISO 8859-1 then it will not be processed as expected. Solution 1 If you use Eclipse then you will notice that it implicitly converts the special character into \uXXXX equivalent. Try … Read more
Maven allows you to define properties in the project’s POM. You can do this using a POM file similar to the following: <project> … <properties> <server.url>http://localhost:8080/manager/html</server.url> </properties> … <build> <plugins> <plugin> … <configuration> <url>${server.url}</url> <server>tomcat</server> </configuration> … </plugin> </plugins> </build> </project> You can avoid specifying the property within the properties tag, and pass the value … Read more
If you have a class of configuration values, like your Constants class, and you want to load all values from a configuration (properties) file, you can create a little helper class and use reflection: public class ConfigLoader { public static void load(Class<?> configClass, String file) { try { Properties props = new Properties(); try (FileInputStream … Read more
The property file task is for editing properties files. It contains all sorts of nice features that allow you to modify entries. For example: <propertyfile file=”build.properties”> <entry key=”build_number” type=”int” operation=”+” value=”1″/> </propertyfile> I’ve incremented my build_number by one. I have no idea what the value was, but it’s now one greater than what it was … Read more
The only way you can inject values into a final field is through Constructor Injection. Everything else would be an awful hack on Spring’s side.
I can suggest using delimiters and using the String.split(delimiter) Example properties file: MON=0800#Something#Something1, Something2 prop.load(new FileInputStream(“\\\\Myseccretnetwork\\Project\\props.properties”)); String[]values = prop.get(“MON”).toString().split(“#”); Hope that helps
With XML config I’ve been using this construct: <context:annotation-config/> <bean id=”yamlProperties” class=”org.springframework.beans.factory.config.YamlPropertiesFactoryBean”> <property name=”resources” value=”classpath:test.yml”/> </bean> <context:property-placeholder properties-ref=”yamlProperties”/> Of course you have to have the snakeyaml dependency on your runtime classpath. I prefer XML config over the java config, but I recon it shouldn’t be hard to convert it. edit: java config for completeness sake … Read more