Difference between revisions of "WebProtegeReleaseNotes"

Revision as of 17:14, August 15, 2009

WebProtege Release Notes

WebProtege 0.5 Alpha Series

Build 200 - August 15, 2009

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:

  # Defaults to false; change to true to run WebProtege in external server mode
  load.ontologies.from.protege.server=true
  
  # Use to specify an alternative location for the metaproject if running in local mode
  local.metaproject.path=/tmp/metaproject.pprj
  
  # Hostname of the Protege server if WebProtege is running in external server mode; can also contain a port number
  server.hostname=localhost
  
  # Username that WebProtege uses to connect to the Protege server if running in external server mode
  webprotege.user=webprotege
  
  # Password that WebProtege uses to connect to the Protege server if running in external server mode
  webprotege.password=webprotege
  
  # Automatic save interval for ontologies if running in local mode (we recommend the database back-end instead of file mode)
  server.save.interval.sec=120
  

  Values of properties listed above should be changed to match your custom WebProtege installation.

• Project configurations are now saved in the <your-servlet-container>/webprotege/projectConfigurations folder. The XML configuration files contain user interface layout information (tabs to display, number of columns in a tab, portlets to display in a tab, portlet properties, etc.). The default configuration file is "configuration.xml". New configuration files are automatically generated if a user saves the layout for a particular project. Configurations are stored per user, per project.
• Users can now open multiple ontologies in WebProtege. Each ontology is displayed in a separate tab.

Other Changes