| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Greetings, |
| 5 |
|
| 6 |
AUDIENCE-- |
| 7 |
This RFC is targeted towards developers working with Java in web services, |
| 8 |
and is intended to address how packages that create WAR files will install |
| 9 |
them. |
| 10 |
|
| 11 |
PROBLEM-- |
| 12 |
Up until about 10 minutes ago, I was writing a java-pkg_dowar() function to |
| 13 |
automatically install WAR files into any servlet engines which are |
| 14 |
currently installed on the machine. However... there's just too much |
| 15 |
undesireable behavior. |
| 16 |
|
| 17 |
For instance, if you have three servlet engines installed (Tomcat, Resin, |
| 18 |
Orion) but are only using one -- Orion -- java-pkg_dowar would install the |
| 19 |
.war file into all three of them, when you only want it in one place. Or |
| 20 |
maybe you want to test the WAR in Tomcat, but normally run Orion. It can |
| 21 |
get messy. |
| 22 |
|
| 23 |
PROPOSED SOLUTION-- |
| 24 |
java-pkg_dowar() will be implemented in the manner described below. |
| 25 |
|
| 26 |
1. War files get installed to ${DESTTREE}/share/${PN}/webapps/. |
| 27 |
2. It will be a best practice to put a note in pkg_postinst() to state |
| 28 |
where the WAR file got installed to during the merge. |
| 29 |
3. It is up to the user to copy the WAR file into whatever engine they |
| 30 |
need it to go, and restart the engine if necessary. |
| 31 |
|
| 32 |
Agreements, criticisms, alternate suggestions? |
| 33 |
|
| 34 |
Cheers, |
| 35 |
Dylan Carlson |
| 36 |
|
| 37 |
Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x708E165F |
| 38 |
Key fingerprint = 3AEA DE38 FE42 15A6 C0E2 730E 3D04 BCC1 708E 165F |
| 39 |
-----BEGIN PGP SIGNATURE----- |
| 40 |
Version: GnuPG v1.2.1 (GNU/Linux) |
| 41 |
|
| 42 |
iD8DBQE+sXagPQS8wXCOFl8RAnd+AJ0ZAI6WTq7YIHkcO/mHVWzk0Nk3EwCfSMuu |
| 43 |
qJ5+GWcagHu73n731u7H52k= |
| 44 |
=PZYZ |
| 45 |
-----END PGP SIGNATURE----- |
| 46 |
|
| 47 |
|
| 48 |
-- |
| 49 |
gentoo-dev@g.o mailing list |
Archives