Difference between revisions of "WebProtegeReleaseNotes"

From Protege Wiki
Jump to: navigation, search
(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))
 
Line 8: Line 8:
 
==== Critical Changes (please read) ====
 
==== Critical Changes (please read) ====
  
 +
<ul>
 
<li>Upgraded to [http://code.google.com/webtoolkit/releases/release-notes-1.7.0.html#Release_Notes_Current GWT 1.7].</li>
 
<li>Upgraded to [http://code.google.com/webtoolkit/releases/release-notes-1.7.0.html#Release_Notes_Current GWT 1.7].</li>
  
Line 13: Line 14:
  
 
<li style="padding-top:5px;">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 <code><your-servlet-container>/webprotege</code> 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:
 
<li style="padding-top:5px;">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 <code><your-servlet-container>/webprotege</code> 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:
−
 
+
<pre>
−
 
+
# Defaults to false; change to true to run WebProtege in external server mode
−
Set to true to use WebProtege in client-server mode; default false
 
 
load.ontologies.from.protege.server=true
 
load.ontologies.from.protege.server=true
  
−
# If you use local mode, specify an alternative location for the metaproject
+
# Use to specify an alternative location for the metaproject if running in local mode
 
local.metaproject.path=/tmp/metaproject.pprj
 
local.metaproject.path=/tmp/metaproject.pprj
  
−
# Hostname of the Protege server to be used if WebProtege runs in client-server mode. It can also contain a port number
+
# Hostname of the Protege server if WebProtege is running in external server mode; can also contain a port number
 
server.hostname=localhost
 
server.hostname=localhost
  
−
# User name that WebProtege uses to connect to the Protege server, if WebProtege runs in client-server mode
+
# Username that WebProtege uses to connect to the Protege server if running in external server mode
 
webprotege.user=webprotege
 
webprotege.user=webprotege
  
−
# Password that WebProtege uses to connect to the Protege server, if WebProtege runs in client-server mode
+
# Password that WebProtege uses to connect to the Protege server if running in external server mode
 
webprotege.password=webprotege
 
webprotege.password=webprotege
  
−
# Automatic save interval for the projects, if WebProtege runs in local mode (recommended to use database backend)
+
# 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
 
server.save.interval.sec=120
 +
</pre>
  
−
The values of the above properties should be changed to match your custom WebProtege installation.
+
Values of properties listed above should be changed to match your custom WebProtege installation.
 +
</li>
  
−
- 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.
+
<li style="padding-top:5px;">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.</li>
  
−
- Users can now open multiple ontologies in WebProtege. Each ontology opens in a different tab.  
+
<li style="padding-top:5px;">Users can now open multiple ontologies in WebProtege. Each ontology is displayed in a separate tab.</li>
 +
</ul>
  
 
==== Other Changes ====
 
==== Other Changes ====

Revision as of 18:13, August 15, 2009

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: 
    # 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

Retrieved from "https://protegewiki.stanford.edu/index.php?title=WebProtegeReleaseNotes&oldid=6444"