Bureaucrats, editor, reviewer, Administrators
13,550
edits
Changes
Jump to navigation
Jump to search
no edit summary
BaseX provides access to stored database resources and to the XQuery engine via [[REST]], can be used as [[RESTXQWeb Application]] and [[WebDAV]] services. This article describes different ways of deploying and configuring these It currently provides three services. The services can be deployed in three different ways:
* [[RESTXQ]] allows you to write web applications with XQuery,* [[REST]] offers a RESTful API for accessing database resources via URLs, and* [[WebDAV]] provides access to databases via the file system. This article describes different ways of deploying and configuring these services. The services can be deployed as follows: * as standalone application by running the [[Startup#Web ApplicationHTTP Server|BaseX HTTP Server]],* as web servlets servlet in a J2EE [[#Servlet Container|Servlet Container]], and* for development purposesas web servlet, using [[#Maven|Maven]].<br/><br/>
=Servlet Container=
In order to deploy BaseX HTTP Services in a servlet container, you may download the WAR distribution of BaseX from the [http://basex.org/download download site] or compile it via <code>mvn compile war:war</code> in the <code>basex-api</code> package. The WAR file can then be deployed following the instructions of the corresponding servlet container ([http://docswww.codehauseclipse.org/displayjetty/JETTYdocumentation/WebAppDeployer current/quickstart-deploying-webapps.html jetty], [http://tomcat.apache.org/tomcat-7.0-doc/deployer-howto.html tomcat]).
Configuring port, context path, etc. can be done by following the corresponding instructions of the used servlet container. This is needed if you want to replace the default URL path (e.g. http://localhost:8080/rest) with a custom one (e.g. http://localhost:8080/BaseX711/rest).
