BaseX provides access to stored database resources and to the XQuery engine via [[REST]], [[RESTXQ]] and [[WebDAV]] services. This article describes different ways of deploying and configuring these services. The services can be deployed in 3 different ways:
* as web servlets in a J2EE servlet container, and* as a standalone application,* for development purposes, using maven, and* as a standalone application.<br/><br/>
=Servlet Container=
</pre>
How to set these options in the web.xml of the BaseX web application is specific to the servlet container. For example, in Jetty it is done using [http://docs.codehaus.org/display/JETTY/override+web.xml an overriding web.xml]. Another option is to decompress the WAR file, edit the WEB-INF/web.xml file and again compress the WAR file.
=Standalone Application=
Detailed description how to start and setup the standalone BaseX HTTP server can found under [[Startup#BaseX HTTP Server|Startup: BaseX HTTP Server]].
=Maven=
==Configuration==
The same options as in the case of deployment in a servlet container apply. In this case, however, there is no WAR archive. Instead Jetty uses the directory {{Mono|basex-api/src/main/webapp}}. For configuring various Jetty runtime options, such as port, context path, etc. refer to the [http://docs.codehaus.org/display/JETTY/Maven+Jetty+Plugin Maven Jetty Plugin]. These should be entered in the {{Mono|pom.xml}} file of the {{Mono|basex-api}} project.
=Standalone Application=
Detailed description how to start and setup the standalone BaseX HTTP server can found under [[Startup#BaseX HTTP Server|Startup: BaseX HTTP Server]].
=Changelog=