WebProtegeReleaseNotes

From Protege Wiki
Revision as of 17:00, August 15, 2009 by JenniferVendetti (talk | contribs) (Created page with '<p style="padding:0; margin:0; font-size:1.9em; font-weight:bold; word-spacing:-2px;">WebProtege Release Notes</p> == WebProtege 0.5 Alpha Series == === Build 200 === ==== Cr...' (checkpoint save))

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

WebProtege Release Notes


WebProtege 0.5 Alpha Series

Build 200

Critical Changes (please read)

  • Upgraded to GWT 1.7.
  • We made some changes to the directory structure and Eclipse setup to conform to GWT 1.7. If you are installing WebProtege, please re-read the Administrator's Guide for updated instructions. Developers should look at the Developer's Guide - the setup for compiling and running WebProtege has been greatly simplified thanks to the Google Plugin for Eclipse.
  • WebProtege now runs in "local mode" by default. Local mode means that WebProtege will load ontologies from a standalone instance of Protege in your Servlet container. WebProtege can also be configured to run in "external server mode" by setting a property value in the protege.properties file in the <your-servlet-container>/webprotege directory. External server mode means that WebProtege will load ontologies from a Protege server running outside of your Servlet container. The following additional configurations options can be set in protege.properties: Set to true to use WebProtege in client-server mode; default false load.ontologies.from.protege.server=true
    1. If you use local mode, specify an alternative location for the metaproject
    local.metaproject.path=/tmp/metaproject.pprj
    1. Hostname of the Protege server to be used if WebProtege runs in client-server mode. It can also contain a port number
    server.hostname=localhost
    1. User name that WebProtege uses to connect to the Protege server, if WebProtege runs in client-server mode
    webprotege.user=webprotege
    1. Password that WebProtege uses to connect to the Protege server, if WebProtege runs in client-server mode
    webprotege.password=webprotege
    1. Automatic save interval for the projects, if WebProtege runs in local mode (recommended to use database backend)
    server.save.interval.sec=120 The values of the above properties should be changed to match your custom WebProtege installation. - Project configurations are now saved in war/projectConfigurations folder. The xml configuration files contain the layout information (tabs to show, number of columns in a tab, portlets to show in a tab, portlet properties, etc.). The default configuration file is configuration.xml. New configuration files are generated if a user saves the layout for a particular project. Configurations can be stored per user / per project. - Users can now open multiple ontologies in WebProtege. Each ontology opens in a different tab. ==== Other Changes ====