Protege Server design - Revision history

Tredmond: /* Plugin Model */

2013-09-13T21:42:04Z

‎Plugin Model

Tredmond: /* Plugin Model */

2013-09-13T21:14:35Z

‎Plugin Model

Tredmond at 21:10, September 13, 2013

2013-09-13T21:10:22Z

Tredmond: /* Plugin Model */ (checkpoint save)

2013-09-13T21:01:59Z

‎Plugin Model: (checkpoint save)

Tredmond: /* Plugin Model */

2013-09-13T19:15:13Z

‎Plugin Model

Tredmond: /* Main concepts */

2013-09-13T19:04:39Z

‎Main concepts

Tredmond: /* Tricky points */

2013-09-13T19:01:53Z

‎Tricky points

Tredmond: /* Protege Server Modules */

2013-09-13T19:01:04Z

‎Protege Server Modules

Tredmond: /* Ontology Serialization */

2013-09-13T19:00:32Z

‎Ontology Serialization

Tredmond: /* Ontology Serialization */

2013-09-13T18:59:51Z

‎Ontology Serialization

@@ Line 27: / Line 27: @@
 While a server may be configured in a programatic fashion, one of the primary methods of running the server uses a plugin architecture. In this plugin architecture, jar files for server plugins are placed in a directory where they are automatically loaded and then configured to work together by following the instructions in a server configuration file.  This plugin mechanism is based on the OSGi declarative services.  There are four main types of extensions that a plugin may make to the Protege OWL Server:
-* A core server.  The server is the core component that implements all the [https://github.com/protegeproject/org.protege.owl.server/blob/master/src/main/java/org/protege/owl/server/api/server/Server.java server interface] which includes both [https://github.com/protegeproject/org.protege.owl.server/blob/master/src/main/java/org/protege/owl/server/api/server/ServerExports.java public interfaces] that are accessible to the client as well as [https://github.com/protegeproject/org.protege.owl.server/blob/master/src/main/java/org/protege/owl/server/api/server/ServerInternals.java server private interfaces] that are only accessible by plugins on the server.
+* A core server.  The server is the core component that implements all the [https://github.com/protegeproject/org.protege.owl.server/blob/master/src/main/java/org/protege/owl/server/api/server/Server.java server interface] which includes both [https://github.com/protegeproject/org.protege.owl.server/blob/master/src/main/java/org/protege/owl/server/api/server/ServerExports.java public interfaces] that are accessible to the client as well as [https://github.com/protegeproject/org.protege.owl.server/blob/master/src/main/java/org/protege/owl/server/api/server/ServerInternals.java server private interfaces] that are only accessible by plugins on the server.  This means that somebody who thinks they have a better implementation of the server interface can simply write a plugin and configure a Protege OWL Server to use their implementation.
-* A server filter extension.  This type of extension intercepts all calls to the server and may perform arbitrary processing either before or after calling the server.  Examples of server filters include
+* A server filter extension.  This type of extension intercepts all calls to the server and may perform arbitrary processing, including throwing an exception, either before or after calling the server.  Examples of server filters that are used by the standard Protege OWL server distribution include
 ** extensions that  check that a given call is consistent with policy,
-** extensions that check that the caller is properly
+** extensions that check that the caller is properly authenticated,
 ==Interfaces==

@@ Line 27: / Line 27: @@
 While a server may be configured in a programatic fashion, one of the primary methods of running the server uses a plugin architecture. In this plugin architecture, jar files for server plugins are placed in a directory where they are automatically loaded and then configured to work together by following the instructions in a server configuration file.  This plugin mechanism is based on the OSGi declarative services.  There are four main types of extensions that a plugin may make to the Protege OWL Server:
-* A core server.  The server is the core component that implements all the [https://github.com/protegeproject/org.protege.owl.server/blob/master/src/main/java/org/protege/owl/server/api/server/Server.java server interface] which includes both [https://github.com/protegeproject/org.protege.owl.server/blob/master/src/main/java/org/protege/owl/server/api/server/ServerExports.java functionality] that is accessible to the client as well as [https://github.com/protegeproject/org.protege.owl.server/blob/master/src/main/java/org/protege/owl/server/api/server/ServerInternals.java server functionality] that is only accessible by plugins on the server.
+* A core server.  The server is the core component that implements all the [https://github.com/protegeproject/org.protege.owl.server/blob/master/src/main/java/org/protege/owl/server/api/server/Server.java server interface] which includes both [https://github.com/protegeproject/org.protege.owl.server/blob/master/src/main/java/org/protege/owl/server/api/server/ServerExports.java public interfaces] that are accessible to the client as well as [https://github.com/protegeproject/org.protege.owl.server/blob/master/src/main/java/org/protege/owl/server/api/server/ServerInternals.java server private interfaces] that are only accessible by plugins on the server.
-* A server filter extension.  This type of extension intercepts all
+* A server filter extension.  This type of extension intercepts all calls to the server and may perform arbitrary processing either before or after calling the server.  Examples of server filters include
+** extensions that  check that a given call is consistent with policy,
 ==Interfaces==

@@ Line 26: / Line 26: @@
 ==Plugin Model==
-While a server may be configured in a programatic fashion, one of the primary methods of running the server uses a plugin architecture. In this plugin architecture, jar files for server plugins are placed in a directory where they are automatically loaded and then configured to work together by following the instructions in a server configuration file.  This plugin mechanism is based on the OSGi declarative services.  Each plugin
+While a server may be configured in a programatic fashion, one of the primary methods of running the server uses a plugin architecture. In this plugin architecture, jar files for server plugins are placed in a directory where they are automatically loaded and then configured to work together by following the instructions in a server configuration file.  This plugin mechanism is based on the OSGi declarative services.  There are four main types of extensions that a plugin may make to the Protege OWL Server:
 ==Interfaces==

@@ Line 26: / Line 26: @@
 ==Plugin Model==
-While a server may be configured in a programatic fashion, one of the primary methods of running the server uses a plugin architecture. In this plugin architecture, jar files for server plugins are placed in a directory where they are automatically loaded and then configured to work together by following the instructions in a server configuration file.
+While a server may be configured in a programatic fashion, one of the primary methods of running the server uses a plugin architecture. In this plugin architecture, jar files for server plugins are placed in a directory where they are automatically loaded and then configured to work together by following the instructions in a server configuration file.  This plugin mechanism is based on the OSGi declarative services.  Each plugin
 ==Interfaces==

← Older revision		Revision as of 19:15, September 13, 2013
Line 26:		Line 26:
	==Plugin Model==		==Plugin Model==

		+	While a server may be configured in a programatic fashion, one of the primary methods of running the server uses a plugin architecture. In this plugin architecture, jar files for server plugins are placed in a directory where they are automatically loaded and then configured to work together by following the instructions in a server configuration file.

	==Interfaces==		==Interfaces==

@@ Line 22: / Line 22: @@
      void commit(AuthToken u, ServerOntologyDocument doc, SingletonChangeHistory changes) throws OWLServerException;
 </pre>
 ==Plugin Model==

← Older revision		Revision as of 19:01, September 13, 2013
Line 40:		Line 40:

	===Update after a commit===		===Update after a commit===
		+
		+
		+	===Out of band interfaces===

← Older revision		Revision as of 19:01, September 13, 2013
Line 32:		Line 32:

	===Serialization of ontology changes===		===Serialization of ontology changes===
		+
		+
		+	==Client side revision management==

	==Tricky points==		==Tricky points==

@@ Line 31: / Line 31: @@
 ==Protege Server Modules==
-===Ontology Serialization===
+===Serialization of ontology changes===
 ==Tricky points==

← Older revision		Revision as of 18:59, September 13, 2013
Line 32:		Line 32:

	===Ontology Serialization===		===Ontology Serialization===
		+
		+
		+	==Tricky points==
		+
		+
		+	===Update after a commit===