FYI, your speculation about the context.xml file was correct. I don't know how I missed that. I thought I had checked it :-) After changing the values there, the application works as expected.
Thanks, Greg On Thu, Apr 10, 2014 at 9:29 PM, Martin Desruisseaux <[email protected]> wrote: > Hello Greg > > Unfortunately I'm not familiar with the sis-webapp module. I saw no > developer name in source code or in the module pom.xml file, so I do not > know who to ask... I will ask on the dev mailing list. In the meantime, > I do not know if it can be of any help, but a search for > "sis-location-config" on the source code has show that the path also > appears in the following file, in addition to web.xml: > > application/sis-webapp/src/main/webapp/META-INF/context.xml > > I hope that sis-webapp has not suffered from the various refactoring > done during the last year... > > Martin > > > Le 10/04/14 14:06, Greg Reddin a écrit : >> I discovered an odd occurrence using the sis-webapp demo. I'm running >> Tomcat 7.0.53 on Mac OSX Mavericks. I took the approach of modifying >> the web.xml file in the source tree (attaching the contents here) and >> running mvm clean package to create the war file. >> >> Then I copied the .war file to Tomcat's web apps directory. >> >> When I tried to do a request to the web page I get an error like the >> following in the log: >> >> [INFO] Existing qtree index at: [/path/to/qtree/index/dir/] not found. >> Creating new index. >> ava.io.FileNotFoundException: /path/to/sis-location-config.xml (No >> such file or directory) >> at java.io.FileInputStream.open(Native Method) >> at java.io.FileInputStream.<init>(FileInputStream.java:120) >> at java.io.FileInputStream.<init>(FileInputStream.java:79) >> at >> org.apache.sis.services.LocationServlet.init(LocationServlet.java:139) >> >> As you can see below I've changed the parameters in web.xml. I don't >> know where it's getting these values from. The default qtree location >> wasn't even in the original xml. I added my own. I've never had an >> issue like this where Tomcat didn't seem to read context-params. Has >> anyone else experienced this? >> >> Thanks, >> Greg >> >> web.xml below: >> >> <web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; >> xmlns="http://java.sun.com/xml/ns/javaee"; >> xmlns:web="http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd"; >> xsi:schemaLocation="http://java.sun.com/xml/ns/javaee >> http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd"; id="WebApp_ID" >> version="2.5"> >> <display-name>Apache SIS</display-name> >> >> <context-param> >> <param-name>org.apache.sis.services.config.qIndexPath</param-name> >> <param-value>/Users/greddin/sis-data/qtree</param-value> >> </context-param> >> >> <context-param> >> <param-name>org.apache.sis.services.config.geodataPath</param-name> >> <param-value>/Users/greddin/sis-data/geodata</param-value> >> </context-param> >> >> <context-param> >> <param-name>org.apache.sis.services.config.filePath</param-name> >> >> <param-value>/Users/greddin/sis-data/sis-location-config.xml</param-value> >> </context-param> >> >> <servlet> >> <servlet-name>LocationServlet</servlet-name> >> <servlet-class>org.apache.sis.services.LocationServlet</servlet-class> >> </servlet> >> <servlet-mapping> >> <servlet-name>LocationServlet</servlet-name> >> <url-pattern>/location</url-pattern> >> </servlet-mapping> >> </web-app> >
