ModjyWarPackaging » History » Version 2
Alan Kennedy, 2009-03-22 08:48 PM
1 | 1 | Alan Kennedy | h1. Modjy WAR packaging |
---|---|---|---|
2 | |||
3 | h2. Why WAR deployment. |
||
4 | |||
5 | When you deploy WSGI web applications in a java servlet container, such as "Apache Tomcat":http://tomcat.apache.org or "Glassfish":https://glassfish.dev.java.net/ , there are two different ways you can deploy |
||
6 | |||
7 | # You deploy your application using a particular directory structure. |
||
8 | # You can deploy your application as a single file. This file is a "WAR file":http://en.wikipedia.org/wiki/WAR_file , and actually is an archive of the same directory structure described above. |
||
9 | |||
10 | So, if your application is working correctly when deployed as a directory structure, then building a WAR file is a very simple extra step. |
||
11 | |||
12 | h2. How to build a WAR file. |
||
13 | |||
14 | First, build the directory structure of your application. If you're not certain how to build this structure, a simple way forward is to take the demo *modjy_webapp* directory from the jython distribution, and tweak that structure to meet your needs. |
||
15 | |||
16 | When you're happy with the contents of the directory hierarchy, execute a command like this, in the top level of your directory hierarchy, e.g. the *modjy_webapp* directory. |
||
17 | |||
18 | <pre> |
||
19 | $JAVA_HOME/bin/jar cvf WARNAME.war . |
||
20 | </pre> |
||
21 | |||
22 | Where WARNAME is the name of the WAR file you want to create, and $JAVA_HOME refers to the location where your JDK or JRE is installed. |
||
23 | |||
24 | h2. Django WAR packaging. |
||
25 | |||
26 | There is a dedicated page for [[ModjyAndDjango|django and modjy]]. |
||
27 | |||
28 | h2. Pylons WAR packaging. |
||
29 | |||
30 | 2 | Alan Kennedy | There is a dedicated page for [[ModjyAndPylons|django and pylons]]. |