You can create class to handle your properties with constructor like private Properties props = null; private MyProperties() throws IOException { FileInputStream propFile = new FileInputStream(FULL_PATH); props = new Properties(System.getProperties()); props. Load(propFile); RegistryManager rm = RegistryManager.singleton(); rm. AddRegistry("MyProperty", this); } public static MyProperties Singelton() { synchronized (MyProperties.
Class) { if (theInstance == null) { try { theInstance = new MyProperties(); } catch (IOException e) { throw new MissingResourceException("Unable to load property file \"" + FULL_PATH + "\"", MyProperties.class.getName(), PROPERTIES_FILENAME); } } } return theInstance; } and than get properties by one method like public static String getProperty(String propertyName) { String value = Singelton().props. GetProperty(propertyName); if (value == null) { LOGGER. Warning("propertyName (" + propertyName + ") not found in property file (" + FULL_PATH + ")"); } return value; } finally in code you can call only String desiredProperty = MyProperties.
GetProperty("propertyKey") some code is missing and some you maybe won't need but you should get the idea if this is what you wanted to do.
You can create class to handle your properties with constructor like private Properties props = null; private MyProperties() throws IOException { FileInputStream propFile = new FileInputStream(FULL_PATH); props = new Properties(System.getProperties()); props. Load(propFile); RegistryManager rm = RegistryManager.singleton(); rm. AddRegistry("MyProperty", this); } public static MyProperties Singelton() { synchronized (MyProperties.
Class) { if (theInstance == null) { try { theInstance = new MyProperties(); } catch (IOException e) { throw new MissingResourceException("Unable to load property file \"" + FULL_PATH + "\"", MyProperties.class.getName(), PROPERTIES_FILENAME); } } } return theInstance; } and than get properties by one method like public static String getProperty(String propertyName) { String value = Singelton().props. GetProperty(propertyName); if (value == null) { LOGGER. Warning("propertyName (" + propertyName + ") not found in property file (" + FULL_PATH + ")"); } return value; } finally in code you can call only String desiredProperty = MyProperties.
GetProperty("propertyKey"); some code is missing and some you maybe won't need but you should get the idea if this is what you wanted to do...
You can use store(Writer writer, String comments) method in Properties class. Write your properties to a StringWriter and use String from it to print on the HTML.
${yourObject.properties. PropertyOne} works. Properties extends Hashtable implement Map and ${map.
Key} gives you the value under that key. But you are not supposed to use a setter from a JSP, so this is only for display purposes. But you can't access it directly from a static field.
You have to add it to some context - request or application. For example, in a ServletContextListener. ContextInitialized(..): servletContext.
AddAttribute("yourProperties", MyClass. Properties); (then you'd have to map the in web. Xml, of course).
If you extended Properties, you probably know exactly which fields you want to have. In that case, it would seem to be better to just a create a POJO (simple object) with those fields and the appropriate getters (and setters and/or constructor as you wish). If you somehow need the dynamic-ness (?) of Properties, ignore this answer.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.