File: README.Debian

package info (click to toggle)
jserv 1.1.2-2
  • links: PTS
  • area: contrib
  • in suites: woody
  • size: 4,584 kB
  • ctags: 3,019
  • sloc: sh: 7,715; java: 6,635; ansic: 5,013; makefile: 814; perl: 39; xml: 32
file content (25 lines) | stat: -rw-r--r-- 1,172 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
- Try to access http://localhost/servlets/IsItWorking to see if JServ is
  working.

- The default setup is to manually start JServ (i.e. not from Apache but
  from the init script /etc/init.d/jserv). You can change this with the
  ApJServManual option in /etc/jserv/jserv.conf.

- If you use manual startup, standard error of servlet classes will be
  redirected to /var/log/jserv.log (or the log file you have specified in
  (etc/jserv/jserv.properties) and to Apache's error log (usually
  /var/log/apache/error.log) for an automatic startup.

- The JVM interpreter and classpath for the servlet engine is always (i.e.
  manual or automatic startup) taken from /etc/jserv/jserv.properties. The
  corresponding options are wrapper.bin,wrapper.bin.parameters and
  wrapper.classpath.

  BE SURE TO ADD THE STANDARD JAVA CLASSES (classes.zip for JDK 1.1) TO
  THIS CLASSPATH, otherwise you might get stange errors like
  ClassNotFoundExpections for correctly installed classes.

- Java servlets can be put into /usr/share/share/java/servlets or you can
  add another repository to the root servlet zone (in
  /etc/jserv/zones/root.properties) and put your classes there.