Changes

Jump to navigation Jump to search
4 bytes removed ,  16:44, 2 August 2013
m
no edit summary
If run on a Jetty server you may use a {{Code|jetty.xml}} file for detailed server configuration. You can e.g. enable SSL connections or Jetty logging. Place the {{Code|jetty.xml}} right next to the {{Code|web.xml}}. For detailed configuration refer to the [http://wiki.eclipse.org/Jetty/Reference/jetty.xml Jetty Documentation]. A sample [https://github.com/BaseXdb/basex-api/blob/master/src/main/webapp/WEB-INF/jetty.xml jetty.xml] is placed in the basex-api package.
 
To run on [http://tomcat.apache.org/ Apache Tomcat], start the tomcat server and add any <code>*.WAR</code> distribution to deploy using the Tomcat web interface (by default located at http://localhost:8080/manager/html/ ).
==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 looks up all files in the directory <code>[https://github.com/BaseXdb/basex-api/tree/master/src/main/webapp basex-api/src/main/webapp]</code>. Jetty and servlet options can be configured in the {{Code|jetty.xml}} and {{Code|web.xml}} files as described above in the [[#Configuration|Servlet Container Configuration]]. The Jetty stop port can be changed in the [http://docs.codehaus.org/display/JETTY/Maven+Jetty+Plugin Maven Jetty Plugin] sesion in the {{Code|pom.xml}} file.
=Tomcat=
 
Get a version of [http://tomcat.apache.org/ Apache Tomcat] and start the server. In the Tomcat web interface (by default at http://localhost:8080/manager/html/ ) one may add a <code>*.WAR</code> distribution to deploy.
=User Management=
editor, reviewer
115

edits

Navigation menu