Hi Roland, On 7/19/2010 9:45 AM, Roland Schweitzer wrote: > I'm trying to come up with some more clever ways to deploy LAS and I > like the way THREDDS builds the content/thredds directory from the war > on start-up which survives new war file deployments and can be customized. > > Is this concept of putting material that needs to survive between > deployments of the war file in TOMCAT_HOME/content a standard for > servlets or convention you adopted? Are there tools that automate > checking and deploying this content directory or did you develop the > logic and code yourself to copy the files from the exploded war file > location to the content directory? The use of the TOMCAT_HOME/content directory for storing configuration files is not a servlet standard nor is it a widely used convention. Thinking about it now, another option would be to set up a directory in the user's home directory, though it would require a scheme to keep the configuration for multiple TDS instances separate. Yes, we developed the code ourselves to check and copy over the initial content from the exploded war content. We also allow TDS admins to change the "content" directory to somewhere outside TOMCAT_HOME as described on this page: http://www.unidata.ucar.edu/projects/THREDDS/tech/tds4.2/reference/InstallOptions.html#ChangeTdsContentDir If you are interested in code level detail, most of the code for all this is in thredds.servlet.ServletUtils and thredds.server.config.TdsContext. Ethan > Thanks as always, > Roland Ticket Details =================== Ticket ID: CZI-169887 Department: Support THREDDS Priority: Normal Status: Closed
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.