Last update : 2019-03-12 (by Stéphane Sire)
Oppidum is an XML-oriented MVC framework written in XQuery / XSLT / Javascript. It allows to develop web applications on top of the eXist-db native XML database.
Oppidum is developped and maintained by Stéphane Sire at Oppidoc.
Oppidum takes a declarative approach to web application development :
- all the application REST mappings are declared in a special
mapping.xmlfile - each mapping entry define a rendering pipeline to render the page
- the first pipeline step generates a model with an XQuery script
- the second pipeline step generates a view with an XSLT transformation
- the last pipeline step injects view fragments of the previous step into a page template
- all the steps above can be optional and the page template generation can trigger further actions
Besides the steps above, Oppidum provides support to skin applications (a skin is a set of CSS and JavaScript files), to implement access control rules with form-based identification and to manage a multi-phases development cycle (dev, test and prod).
Oppidum is designed to support the creation of reusable modules that can be aggregated together through the mapping mechanism to create complete web applications. Each module is a set of conventions (usually associated with XML vocabularies) and XQuery, XSLT, JavaScript, CSS files.
Oppidum runs out of the box on computers running Linux and Apple OS X. We haven't tested it on windows computer yet, there should be some issues with path separator in the library code.
The master branch is the stable release branch. It contains the Oppidum current version. It is currently compatible with eXist-2.x, eXist-3.x and eXist-4.x
The devel branch is the development branch of Oppidum current version. You should not install it in production.
The test branch is a pre-release branch. You should not install it in production.
The oppidum-1 branch is an archived branch on which we do not plan any evolution. It is required if your application is running with eXist-1.4.3.
Some specific branch may be used to prepare Oppidum next release in particular to adapt to new eXist-DB versions before they are supported in the master (or devel) branch.
-
install the latest stable release of eXist-db on your system first
-
create a project folder that will contain your oppidum applications directly inside the
webappfolder of your eXist installation, by default you should call it projects -
clone Oppidum inside your projects folder. This should create an
oppidumfolder into your projects folder -
start eXist-DB then go inside the
oppidum/scriptsfolder and execute./bootstrap.shto install some oppidum resources into the database, passing it the database admin password as a parameter -
that's it ! You can now point your browser to
http://localhost:8080/exist/projects/oppidumto open the Oppidum developer tools
In summary :
cd {EXIST_HOME}/webapp
mkdir projects
cd projects
git clone https://github.com/ssire/oppidum.git
# or git clone git://github.com/ssire/oppidum.git if you have setup ssh with your github account
cd oppidum/scripts
./bootstrap.sh password
You can install and run several eXist-DB instances on your computer, for that purpose you can edit the EXIST_HOME/tools/jetty/etc/jetty.conf configuration file for each installation so that they run on different ports.
The installer script from the developer tools deduces the project folder name (e.g. projects) from the request URI. In case you want to run it behind a forward proxy configured with path URL rewrite (i.e. to hide out /exist prefix in URLs), then you can manually create a settings.xml file with the name of you project folder inside a ProjectFolderName element :
<Settings>
<ProjectFolderName>projects</ProjectFolderName>
</Settings>
and store it inside your application /db/www/{application}/config collection. This should not be necessary since when using a forward proxy you usually access the Oppidum IDE (and installer) from an SSH tunnel.
The Oppidum documentation contained in the docs folder is also published on the Oppidum site thanks to the Git Hub project pages mechanism. This is still a work in progress.
You can also visit the Oppidum wiki to get more documentation and to learn about the roadmap.
There is a tutorial repository that contains a simple web application written with Oppidum to get started.
We have also setup an oppidum-dev Google group to share assistance and discuss new features.
As a general introduction you can read the XML London 2013 presentation of Oppidum.
Oppidum has been developped to take benefits of AXEL (Adaptable XML Editing Library). This is a JavaScript client-side library for generating document editors into web pages. It works by transforming XTiger XML document templates into editable documents. The templates are XHTML files enriched with instructions to control editing. It can be used together with the AXEL-FORMS extensions to create form-oriented user interfaces with dynamic constraints checking.
Some Oppidum modules are available as third party projects to speed up application development (e.g. image or file upload, forms generator, etc.). You are encouraged to develop and share your own modules. Please [contact us](mailto:s.sire@oppidoc.fr?subject=Oppidum specific needs) if you have specific needs.
The source code of Oppidum is released as free software, under the terms of the LGPL, please make sure that you read the license file at http://www.gnu.org/copyleft/lesser.html.
Oppidum is Open Source and may be used in academic, non-commercial and commercial applications.
Oppidum is standalone software written in XQuery, XSLT and JavaScript. The current version is tailored to run inside eXist-db environment.
[DEPRECATED] For convenience the repository includes the following pre-built libraries for web application development :
- AXEL (http://ssire.github.com/axel/)
- AXEL-FORMS (http://ssire.github.com/axel-forms/)
- 960 grid system (http://960.gs/)
- JQuery (http://jquery.com/)
- JQuery UI subset (http://jqueryui.com/)
- Modernizr subset (http://modernizr.com/)
As we plan to limit the use of the pre-built libraries to the one needed for the Oppidum developer tools, we advise you to directly embed the pre-built libraries that you need directly in you application directory / code depot, and not depend on the ones shipped with Oppidum.