How to use

getPropertiesFromFile

method

in

com.arjuna.common.util.propertyservice.AbstractPropertiesFactory

public static Properties getPropertiesFromFile(String propertyFileName, ClassLoader classLoader) {
  initPropertiesFactory();
  return delegatePropertiesFactory.getPropertiesFromFile(propertyFileName, classLoader);
}

public static Properties getPropertiesFromFile(String propertyFileName, ClassLoader classLoader) {
  initPropertiesFactory();
  return delegatePropertiesFactory.getPropertiesFromFile(propertyFileName, classLoader);
}

public static Properties getPropertiesFromFile(String propertyFileName, ClassLoader classLoader) {
  initPropertiesFactory();
  return delegatePropertiesFactory.getPropertiesFromFile(propertyFileName, classLoader);
}

public static Properties getPropertiesFromFile(String propertyFileName, ClassLoader classLoader) {
  initPropertiesFactory();
  return delegatePropertiesFactory.getPropertiesFromFile(propertyFileName, classLoader);
}

public static Properties getPropertiesFromFile(String propertyFileName, ClassLoader classLoader) {
  initPropertiesFactory();
  return delegatePropertiesFactory.getPropertiesFromFile(propertyFileName, classLoader);
}

private synchronized void initDefaultProperties(String fileNamePropertyKey) {
  if(defaultProperties != null) {
    return;
  }
  // This is where the properties loading takes place. The algorithm is as follows:
  // If the specified fileNamePropertyKey exists as a key is the system properties, take the value of that property as
  // the location of the module's properties file. This allows file location to be overriden easily.
  String propertyFileName = System.getProperty(fileNamePropertyKey);
  // If the system property is not set, try to load the build time properties. Build time properties
  // are not the module properties! These are optional and so loading may fail. That's not considered an error.
  // If the properties file name is defined by the build time properties, use that.
  // (In JBossTS it mostly does exist - the build scripts put build time properties into the .jars manifest file.)
  if (propertyFileName == null) {
    propertyFileName = ConfigurationInfo.getPropertiesFile();
  }
  // Bail out if it has not been possible to get a file name by either of these method.
  if(propertyFileName == null) {
    throw new RuntimeException("Unable to resolve property file name");
  }
  defaultProperties = getPropertiesFromFile(propertyFileName, PropertiesFactoryStax.class.getClassLoader());
}

private synchronized void initDefaultProperties(String fileNamePropertyKey) {
  if(defaultProperties != null) {
    return;
  }
  // This is where the properties loading takes place. The algorithm is as follows:
  // If the specified fileNamePropertyKey exists as a key is the system properties, take the value of that property as
  // the location of the module's properties file. This allows file location to be overriden easily.
  String propertyFileName = System.getProperty(fileNamePropertyKey);
  // If the system property is not set, try to load the build time properties. Build time properties
  // are not the module properties! These are optional and so loading may fail. That's not considered an error.
  // If the properties file name is defined by the build time properties, use that.
  // (In JBossTS it mostly does exist - the build scripts put build time properties into the .jars manifest file.)
  if (propertyFileName == null) {
    propertyFileName = ConfigurationInfo.getPropertiesFile();
  }
  // Bail out if it has not been possible to get a file name by either of these method.
  if(propertyFileName == null) {
    throw new RuntimeException("Unable to resolve property file name");
  }
  defaultProperties = getPropertiesFromFile(propertyFileName, PropertiesFactoryStax.class.getClassLoader());
}

private synchronized void initDefaultProperties(String fileNamePropertyKey) {
  if(defaultProperties != null) {
    return;
  }
  // This is where the properties loading takes place. The algorithm is as follows:
  // If the specified fileNamePropertyKey exists as a key is the system properties, take the value of that property as
  // the location of the module's properties file. This allows file location to be overriden easily.
  String propertyFileName = System.getProperty(fileNamePropertyKey);
  // If the system property is not set, try to load the build time properties. Build time properties
  // are not the module properties! These are optional and so loading may fail. That's not considered an error.
  // If the properties file name is defined by the build time properties, use that.
  // (In JBossTS it mostly does exist - the build scripts put build time properties into the .jars manifest file.)
  if (propertyFileName == null) {
    propertyFileName = ConfigurationInfo.getPropertiesFile();
  }
  // Bail out if it has not been possible to get a file name by either of these method.
  if(propertyFileName == null) {
    throw new RuntimeException("Unable to resolve property file name");
  }
  defaultProperties = getPropertiesFromFile(propertyFileName, PropertiesFactoryStax.class.getClassLoader());
}

private synchronized void initDefaultProperties(String fileNamePropertyKey) {
  if(defaultProperties != null) {
    return;
  }
  // This is where the properties loading takes place. The algorithm is as follows:
  // If the specified fileNamePropertyKey exists as a key is the system properties, take the value of that property as
  // the location of the module's properties file. This allows file location to be overriden easily.
  String propertyFileName = System.getProperty(fileNamePropertyKey);
  // If the system property is not set, try to load the build time properties. Build time properties
  // are not the module properties! These are optional and so loading may fail. That's not considered an error.
  // If the properties file name is defined by the build time properties, use that.
  // (In JBossTS it mostly does exist - the build scripts put build time properties into the .jars manifest file.)
  if (propertyFileName == null) {
    propertyFileName = ConfigurationInfo.getPropertiesFile();
  }
  // Bail out if it has not been possible to get a file name by either of these method.
  if(propertyFileName == null) {
    throw new RuntimeException("Unable to resolve property file name");
  }
  defaultProperties = getPropertiesFromFile(propertyFileName, PropertiesFactoryStax.class.getClassLoader());
}

private synchronized void initDefaultProperties(String fileNamePropertyKey) {
  if(defaultProperties != null) {
    return;
  }
  // This is where the properties loading takes place. The algorithm is as follows:
  // If the specified fileNamePropertyKey exists as a key is the system properties, take the value of that property as
  // the location of the module's properties file. This allows file location to be overriden easily.
  String propertyFileName = System.getProperty(fileNamePropertyKey);
  // If the system property is not set, try to load the build time properties. Build time properties
  // are not the module properties! These are optional and so loading may fail. That's not considered an error.
  // If the properties file name is defined by the build time properties, use that.
  // (In JBossTS it mostly does exist - the build scripts put build time properties into the .jars manifest file.)
  if (propertyFileName == null) {
    propertyFileName = ConfigurationInfo.getPropertiesFile();
  }
  // Bail out if it has not been possible to get a file name by either of these method.
  if(propertyFileName == null) {
    throw new RuntimeException("Unable to resolve property file name");
  }
  defaultProperties = getPropertiesFromFile(propertyFileName, PropertiesFactoryStax.class.getClassLoader());
}