private static PropertyHelper ph = null;\r
\r
/**\r
- * Ways to fix path problem: \r
- * 1) find a path to WEB-INF directory based on the path to a known class. \r
- * Then prepend this absolute path to the rest of paths \r
- * pros: no input from user \r
- * cons: relocation of the source may cause problems \r
+ * Ways to fix path problem: 1) find a path to WEB-INF directory based on\r
+ * the path to a known class. Then prepend this absolute path to the rest of\r
+ * paths pros: no input from user cons: relocation of the source may cause\r
+ * problems\r
* \r
- * 2) Require users to add configuration directories to the class\r
- * path and then load entries from it. \r
- * pros: \r
- * cons: Many paths needs to be added. Put significant burden on the user. \r
- * Hard to tell web appl server to add these entries to its class path. \r
+ * 2) Require users to add configuration directories to the class path and\r
+ * then load entries from it. pros: cons: Many paths needs to be added. Put\r
+ * significant burden on the user. Hard to tell web appl server to add these\r
+ * entries to its class path.\r
* \r
- * 3) Ask for project source directory explicitly in the configuration. \r
- * pros:\r
- * cons: similar to 1, but this initial configuration file must reside in \r
- * well known location! Why ask users what can be found automatically?\r
+ * 3) Ask for project source directory explicitly in the configuration.\r
+ * pros: cons: similar to 1, but this initial configuration file must reside\r
+ * in well known location! Why ask users what can be found automatically?\r
* \r
- * 4) Have everything in the location already in class path for tomcat. \r
- * pros:\r
- * cons: only classes and lib/*.jar are added, Eclipse will remove non \r
+ * 4) Have everything in the location already in class path for tomcat.\r
+ * pros: cons: only classes and lib/*.jar are added, Eclipse will remove non\r
* classses from classes dir.\r
* \r
* Try 1 - succeed.\r
\r
/**\r
* Method return the absolute path to the project root directory. It assumes\r
- * the following structure of the project:\r
- * project-root: \r
- * conf/settings\r
- * binaries \r
- * WEB-INF/classes/compbio/engine/conf/PropertyHelperManager.class\r
+ * the following structure of the project: project-root: conf/settings\r
+ * binaries WEB-INF/classes/compbio/engine/conf/PropertyHelperManager.class\r
* If the structure changes it must be reflected in this method\r
* \r
* @return the local path\r
} catch (IllegalArgumentException e) {\r
// Classes are in the jar file, using different method to determine\r
// the path new File(INCORRECT URL) throws it\r
- String mes = "It looks like classes are in the jar file. " \r
- + "Attempting a different method to determinine the path to the resources";\r
+ String mes = "It looks like classes are in the jar file. "\r
+ + "Attempting a different method to determinine the path to the resources";\r
log.debug(mes + e.getLocalizedMessage(), e.getCause());\r
try {\r
f = new File(ProteoCachePropertyHelperManager.class.getProtectionDomain().getCodeSource().getLocation().toURI().getPath());\r
return Boolean.parseBoolean(propValue);\r
}\r
return false;\r
- }}\r
+ }\r
+}\r