Project

General

Profile

Actions

WebApps » History » Revision 3

« Previous | Revision 3/7 (diff) | Next »
Gregg -, 09/10/2009 09:34 AM
Notes on structure of EmbeddedMulgaraServer, HttpServices


= Web Application Architecture =

Mulgara is designed to work as an embedded component. The standard distribution includes a variety of build configurations, including a web services application.

See [http://mulgara.org/pipermail/mulgara-general/2009-September/000935.html this message] for info on how the default app is structured.

In directory src/jar/server/java/org/mulgara/server:

  • org.mulgara.server.EmbeddedMulgaraServer * "main" - entry point for default server? * sets up configuration, options parsing, etc. * creates instance of EmbeddedMulgaraServer, whose constuctor * creates a Mulgara Server instance (a "ServerMBean", which is an RMI server) * creates an HttpServices intance, passing itself, hostname, and MulgaraConfig as args * launches its services (i.e. Mulgara and webserver) via "startServices", which * invokes {{{init()}}} and {{{start()}}} on the Mulgara Server instance * launches HttpServices instance (which maintains reference to {{{this}}} so it can access the Mulgara server instance) * implements SessionFactoryProvider (in src/jar/query/java/org/mulgara/server/?) * reads config parms using MulgaraConfig object
  • org.mulgara.server.HttpServices * no inheritance * retains reference to Mulgara Server instance * references Jetty stuff
  • org.mulgara.server.AbstractServer implements ServerMBean (?)

In directory src/jar/querylang/java/org/mulgara/protocol/http:

  • javax.servlet.http.HttpServlet * org.mulgara.protocol.http.MulgaraServlet * org.mulgara.protocol.http.ProtocolServlet * org.mulgara.protocol.http.SparqlServlet * org.mulgara.protocol.http.TqlServlet

Updated by Gregg - over 14 years ago · 3 revisions