Skip to content

GumTree Server_4882637

Jump to bottom
nxi edited this page Apr 9, 2015 · 1 revision
Created by Tony Lam, last modified on Jul 06, 2009

Introduction

With the advance of Equinox technology (Eclipse's implementation of OSGi specification), GumTree can now be run as a standalone HTTP server that accepts servlet and JSP requests. GumTree server has provided the following advantages:
  • All non-UI code can be reused.  For example, code that is used for communicate with the SICS control system has been reused to build the web status for SICS.
  • The HTTP server is implemented by pure Java.  This makes the deployment of the GumTree server much more easier.

GumTree Feature Structure

After the official release of Eclipse 3.3 (Europa), GumTree has gone under a structural refactor to align with the latest Eclipse's plug-in structure.  In Eclipse 3.3, many plug-ins have been introduced by the Equinox team to enable server mode operation.  During the GumTree ISEE refactoring, those equinox plug-ins, together with many non-UI Eclipse plug-ins, have been grouped into a new feature called org.gumtree.platform.base.  Using the plug-ins within this base feature enables developers to build application that can run in server mode.  A detailed plug-in list for org.gumtree.platfome.base can be found here. All other required plug-ins for the client mode have been moved into a new feature called org.gumtree.platform.isee.  This feature is built on top of the org.gumtree.platform.base feature.  A detailed plug-in list for the isee feature can be found here.  For making RCP export easier, both both server/base side feature (org.gumtree.platform.base) and client side feature (org.gumtree.platform.isee) are included in the feature org.gumtree.platform.  Developers can build their RCP product by simply including the org.gumtree.platform feature.

GumTree Server Mode

There are two ways to run GumTree based applications in server mode:
  • Equinox launcher mode
    • The main application is this mode is the Equinox launcher.  In this mode, users have the flexibility to manually active any plug-ins, and run multiple RCP application within Equinox in headless mode.
  • Eclipse RCP headless mode
    • The main application is the single RCP application.  In this mode, the main RCP application is responsible (programmatically) to activate the Jetty plug-in (org.eclipse.equinox.http.jetty) to enable the HTTP service.  Another alternative is to manually config the config.ini file for the RCP.
 
Document generated by Confluence on Apr 01, 2015 00:11

Home | Developer Guide | Copyright © 2013 ANSTO

Clone this wiki locally