WebDAV网关 Davenport.7z

---------------------------------------------------------------------- $Id: README.TXT,v 3.110.2.3 2003/11/19 11:23:07 gregwilkins Exp $ ---------------------------------------------------------------------- Jetty 4 ======= Jetty is an Open Source HTTP Servlet Server written in 100% Java. It is designed to be light weight, high performance, embeddable, extensible and flexible, thus making it an ideal platform for serving dynamic HTTP requests from any Java application. Downloading ============ Jetty is can be downloaded in one of the following distribution files: Jetty-X.X.X.tar.gz - This is the complete release containing source, compiled jars, external jars and demos. Installation is simply untaring the tar.gz file in the directory required. Jetty-X.X.X-no-ext.tar.gz - This is the complete release with the external jars removed. This release is good if you already have the required external jars (see below). Jetty-X.X.X-src.tar.gz - A source only distribution which needs to be build using ant. This distribution also excludes the demo. Package contents ================ src - The source for the HTTP server and servlet container. lib - The jars of the compile jetty code. ext - The external jars needed for the main jetty server. etc - The config files and resources. demo - Demos of the HTTP server and servlet container. test - Test harnesses. webapps - The default location for war files or webapps. extra - Directory of optional extras /plus - Extended jetty with JNDI, transaction, JAAS & log4j /ftp - FTP client /j2ee - J2EE distributions and integration /jdk1.2 - Classes for JDK < 1.4 /loadbalancer - A simple load balancer Quick Start =========== Unpack the full jetty release Jetty-X.X.X.tar.gz using an archive tool such as tar or winzip. The server can be run with the commands cd Jetty-X.X.X java -jar start.jar Then point your browser at http://localhost:8080 to see the web site. The demo configuration file can be run with: java -jar start.jar etc/admin.xml etc/demo.xml The JMX variants may be started with java -Dstart.class=org.mortbay.util.jmx.Main -jar start.jar etc/jetty.mlet or java -Dstart.class=org.mortbay.util.jmx.Main -jar start.jar etc/demo.mlet Starting Jetty ============== In order to start Jetty the following steps must be taken: 1) Setting the classpath to the appropriate jars in $JETTY_HOME/lib 2) Adding to the classpath any jars from $JETTY_HOME/ext that your java environment does not provide. 3) If using JSPs, add the tools.jar from your JRE lib and ant.jar from jakarta-ant-1.5 to the classpath. 4) Running "java org.mortbay.jetty.Server <configfile>" Several different mechanisms have been provided to automate this process and you should pick the one that best suits your environment. Jetty start.jar =============== The start.jar file in the Jetty distribution may be run with java -jar start.jar <configfile> ... For example java -jar start.jar etc/admin.xml etc/demo.xml On some systems with graphical file browsers, it may be possible to start jetty by double clicking on this jar file. For more details see $JETTY_HOME/src/org/mortbay/start/README.txt or http://jetty.mortbay.org/javadoc/org/mortbay/start/Main.html If jetty is not being started from the current directory, then the jetty.home property should be set: java -Djetty.home=C:\jetty -jar start.jar <configfile> ... If JSPs do not work with this start method, you may want to clearly specify the location of the JDK so the compiler can be accessed: java -Djava.home=C:\j2sdk1.4.1 -jar start.jar <configfile> ... If an extra classpaths are needed, they can be added with the jetty.class.path property: java -Djetty.class.path=/usr/share/java -jar start.jar <configfile> ... If no configuration file is provided, start.jar will use etc/admin.xml and etc/jetty.xml Programs started with the start.jar mechanism may be stopped with the stop.jar: java -jar stop.jar This connects via a local port to stop the server. The default port can be set with the STOP.PORT system property (default of 8079 and a port of < 0 disables the stop mechanism). If the STOP.KEY system property is set, then a random key is generated and written to stdout. This key must be passed to the stop.jar. eg [540] java -DSTOP.PORT=9999 -DSTOP.KEY -jar start.jar 1rukbu7owi3uo 17:39:49.082 EVENT Starting Jetty/4.2.10pre0 ... [526] java -DSTOP.PORT=9999 -DSTOP.KEY=1rukbu7owi3uo -jar stop.jar Starting with Ant ================= If you have the ant java build tool ant installed, you may use that to start jetty. The demo can be started with: Unix: ant demo Win32: ant.bat demo The JMX enabled demo can be started with Unix: ant demo.jmx Win32: ant.bat demo.jmx The default jetty.xml configuration can be started with: Unix: ant run Win32: ant.bat run An alternative configuration file can be run with Unix: ant -Djetty.run=acme.xml run Win32: ant.bat -Djetty.run=acme.xml run Win32 Service ============= The extra/win32 directory contains instructions of how to start Jetty as a win32 service. Manual Start ============ If you are using jdk1.4, you should use the path (or non-unix equivalent): CLASSPATH=\ $JETTY_HOME/lib/org.mortbay.jetty.jar:\ $JETTY_HOME/lib/javax.servlet.jar:\ $JETTY_HOME/ext/jasper-runtime.jar:\ $JETTY_HOME/ext/jasper-compiler.jar:\ $JETTY_HOME/ext/xercesImpl.jar For jdk1.2 or jdk1.3 us the following classpath, you need to use an alternative jetty jars and add the XML support. Thus the classpath to use is: CLASSPATH=\ $JETTY_HOME/lib/org.mortbay.jetty-jdk1.2.jar:\ $JETTY_HOME/lib/javax.servlet.jar:\ $JETTY_HOME/ext/jasper-runtime.jar:\ $JETTY_HOME/ext/jasper-compiler.jar:\ $JETTY_HOME/ext/xercesImpl.jar:\ $JETTY_HOME/ext/xml-apis.jar:\ $JETTY_HOME/ext/xmlParserAPIs.jar To use the default SSL provider you may also need to add the the jars below, which is a merge of the jsse, jnet and jcert jars from the JSSE package (see $JETTY_HOME/demo/webapps/jetty/doc/JsseSSL.html for more details): $JETTY_HOME/ext/jnet.jar (not required for JDK 1.4.1) $JETTY_HOME/ext/jcert.jar $JETTY_HOME/ext/jsse.jar To use JMX the classpath must also include: $JETTY_HOME/ext/jmxri.jar $JETTY_HOME/ext/jmxtools.jar To run JSP with the JDK compiler, you will also need to add the jar containing the JDK compiler (if you wish to use another compiler you will have to configure jasper) and the ant.jar from jakarta-ant 1.5 or later. If your JVM supports the -server flag, then it can be a useful option to include when starting Jetty. It can reduce memory size and avoid some JVM crashes. External Jars ============= The ext directories within the Jetty hierarchy contain external libraries that are required to compile run Jetty. Many of these jars may now be provided by your JVM or elsewhere on your classpath. If so, these jars can probably be safely removed from the Jetty distribution. A SAX XML parser is required by webapp components of Jetty and the xerces parser is included as well as the javax apis for this: $JETTY_HOME/ext/xercesImpl.jar $JETTY_HOME/ext/xml-apis.jar $JETTY_HOME/ext/xmlParserAPIs.jar If JSP is to be used, then the Jasper jars from jakarta and an ant jar must be present. Jetty includes Jasper2, but jasper1 may be safely substituted: $JETTY_HOME/ext/jasper-compiler.jar $JETTY_HOME/ext/jasper-runtime.jar $JETTY_HOME/ext/ant.jar If SSL is to be used then the JSSE libraries may need to be present plus the reference implementation from sun: $JETTY_HOME/ext/jnet.jar $JETTY_HOME/ext/jcert.jar $JETTY_HOME/ext/jsse.jar If SSL is to be used, then the JMX library and tools ne