Page Comparison

...

• ValidatoinResult precheckLoadFromSourceData
• Application hardening
  • Error handling during configuration (bad db, username, password)
  • directory already exists?
  • DONE failed load
    • sourceData marked as FAILED -> only support certain actions
  • DONE cancelled load -> allow reload of delta
  • source data missing, some terminology data loaded
• spelling.txt, acronyms.txt
  • package these files into the war. (so they are in WEB-INF/classes)
  • getResourceAsStream("spelling.txt") -> source.data.dir/spelling.txt
• Single Download Terminology Starter Kit - ...
  • Run the .war file via Jetty all packaged as an exectuable .jar
  • Single zip file download containing
    • termserver.jar
    • data/ (spelling.txt, acronyms.txt)
    • indexes/ (lucene indexes)
    • hsqldb/ (database files) 
  • config.properties
    • Uses "hsqldb" jdbc (with "file" not "mem" mode)
      • http://stackoverflow.com/questions/3804409/using-hsql-in-memory-database-as-jpa-datasource
    • directories can all be relative (which should work relative to the executable .jar file).
  • StarterKitApplication (e.g. the jersey application)
    • initialization hook to start the hsqldb server - http://stackoverflow.com/questions/3660502/how-can-i-start-and-keep-running-hsqldb-in-server-mode-from-within-my-web-applic
  • Maven process
    • ssk-rest (module)
      • Build .war file
      • .war file must contain a completely ready config.properties file (e.g. in WEB-INF/classes) - put in src/main/resources 
        • no filtering required
        • exact hsqldb jdbc url, user, password
        • indexBase=./indexes
        • spellingFile=./data/spelling.txt
        • security.guest.disabled=false
        • mail server??
        • landing/ login/ intro page configuration
    • ssk-app/ (module)
    • pom.xml
      • Load database  (Rrf2SnapshotSourceDataLoadMojo)
        • specify indexes directory        (${project.build.dir}/app/indexes
        • specify hsqldb directory          (${project.build.dir}/app/db)
        • specify snomed (or input dir)  (-Dinput.dir)
      • Gather all resources into ${project.build.dir}/app
        • packages .war file (from ssk-rest) as an executable .jar that runs jetty, snomed-starter-kit.jar
        • package spelling.txt and acronyms.txt files in ${project.build.dir}/app/data
      • Use assembly plugin to zip everything from ${project.build.dir}/app/* into snomed-starter-kit.zip
• DONE: Get initial starter kit running

...