From 0dfeb7cc94c619e427094c69d0cdeb14028212cb Mon Sep 17 00:00:00 2001 From: "Niels Erik G. Nielsen" Date: Mon, 10 Jun 2013 19:09:09 -0400 Subject: [PATCH] Fixing web.xml based config example --- src/main/java/com/indexdata/mkjsf/config/package-info.java | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/src/main/java/com/indexdata/mkjsf/config/package-info.java b/src/main/java/com/indexdata/mkjsf/config/package-info.java index 6716e66..aec5200 100644 --- a/src/main/java/com/indexdata/mkjsf/config/package-info.java +++ b/src/main/java/com/indexdata/mkjsf/config/package-info.java @@ -31,17 +31,23 @@ * * *

For the web.xml configuration scheme (choosing WebXmlConfigReader in beans.xml) - * to pre-define the URL of the Pazpar2 to use, the configuration could be:

+ * to pre-define the URL of the Pazpar2 to use and choose Pazpar2 as the selected + * service type, the configuration could be:

* * 
  *  <context-param>
  *   <param-name>PAZPAR2_URL</param-name>
  *   <param-value>http://localhost:8004/</param-value>
  *  </context-param>
+ *  <context-param>
+ *   <description>Service type. Possible values: SP, PZ2, TBD</description>
+ *   <param-name>TYPE</param-name>
+ *   <param-value>PZ2</param-value>  
+ *  </context-param>
  *
* *

For the Mk2ConfigReader scheme to work, the web.xml must then contain pointers to the configuration directory - * and properties file. + * and properties file. The specific configuration itself would be in those files then. * In this example the configuration directory is in the web application itself (war://testconfig). A more regular * example would put it in a separate directory to not have it overwritten by each deployment of the war.

* 
-- 
1.7.10.4