1 |
Hello, |
2 |
|
3 |
I am looking into making webapp-config Java-aware. While there are quite a few |
4 |
things that would need to happen from both the w-c and Java ends, it definitely |
5 |
seems plausible. |
6 |
|
7 |
The first step is to develop a directory structure for Java webapps that |
8 |
supports virtual hosts and plays nice with GLEP 11. All four J2EE/servlet |
9 |
engines currently in Portage (tomcat, jetty, resin, and jboss) implement this in |
10 |
their own way: |
11 |
|
12 |
- tomcat stores webapps in /var/lib/tomcat-5/{vhost}/webapps. There is |
13 |
one "default" vhost. |
14 |
- jetty stores webapps in /opt/jetty/webapps. There is currently no |
15 |
vhost hierarchy, although I believe it should be easy to create one under |
16 |
/opt/jetty/webapps/{vhost} |
17 |
- resin stores webapps in /opt/resin/webapps. There is currently no |
18 |
vhost hierarchy, although I believe it should be easy to create one under |
19 |
/opt/resin/webapps/{vhost} |
20 |
- jboss is less straightforward. It appears that webapps go into |
21 |
/var/lib/jboss/{all,default,minimal}, but I'm not sure what the difference |
22 |
between those three directories is or how vhosts are handled. |
23 |
|
24 |
I propose to add a Java-specific directory under /var/www/{vhost}, such as |
25 |
/var/www/localhost/java (perhaps there is a better name than java?). This |
26 |
directory could be symlinked from the tomcat/jetty/resin/jboss locations, much |
27 |
like what tomcat already does. This would have the benefit of keeping everything |
28 |
related to one vhost (statis HTML, servlets, CGI scripts, etc) in one location. |
29 |
|
30 |
Comments and suggestions (esp. from Java folks) are welcome. I would |
31 |
particularly like to figure out what to do with jboss. |
32 |
|
33 |
-- |
34 |
Renat Lumpau |
35 |
all things web-apps |
36 |
GPG key id #C6A838DA on http://pgp.mit.edu |
37 |
Key fingerprint = 04AF B5EE 17CB 1000 DDA5 D3FC 1338 ADC2 C6A8 38DA |