Raible's Wiki: AppFuseOnWinstone

At line 5 changed 1 line.

__1.__ Build AppFuse as usual: {{ant war}};

__1.__ Build AppFuse as usual (project name: {{felini}}): {{ant war}};

At line 7 changed 1 line.

__2.__ Create a directory, for example, {felini} and on it another sub-directory: {lib};

__2.__ Create a directory, for example, {{felini}} and on it a sub-directory: {{lib}};

At line 9 changed 1 line.

__3.__ Copy your war file to felini and copy your JBDC Driver and jta.jar to lib directory;

__3.__ Download [Winstone|http://winstone.sourceforge.net/] into the {{felini}} directory, the version I will use is: {{winstone-0.8.1.jar}};

At line 11 changed 1 line.

__4.__ Other thing, in order to turn on JSP compilation in [Winstone|http://winstone.sourceforge.net/], you'll need to place the following jar files into the lib folder under the current directory (or the folder identified by the --commonLibFolder directive): jasper-compiler.jar, jasper-runtime.jar, ant.jar, commons-logging-api.jar, commons-el.jar (Jasper 2 only) - These are required if you are using Jasper 2.0. You can get them from the tomcat binary distribution;

__4.__ Copy your war file to {{felini}} directory;

__5.__ Other thing, in order to turn on JSP compilation in [Winstone|http://winstone.sourceforge.net/], you'll need to place the following jar files into the {{lib}} folder under the current directory (or the folder identified by the --commonLibFolder directive): jasper-compiler.jar, jasper-runtime.jar, ant.jar, commons-logging-api.jar, commons-el.jar (Jasper 2 only) - These are required if you are using Jasper 2.0. You can get them from the tomcat binary distribution;

__6.__ From the {{felini}} directory run:

<pre>java -jar winstone-0.8.1.jar --warfile=feline.war --useJasper</pre>

That's it! No more no less! But wait, it has more ...

%%note __NOTE:__ This is from Winstone docs:

<h2><a name="embedding">Embedding Winstone</a></h2>

The design of Winstone has always allowed its easy embedding within another application. It's as simple

as:

<pre> // at startup

Map args = new HashMap();

args.put("webroot", "<my webroot dir>"); // or any other command line args, eg port

Launcher.initLogger(args);

Launcher winstone = new Launcher(args); // spawns threads, so your application doesn't block

... (your application code)

// before shutdown

winstone.shutdown(); </pre>

From v0.8 though, there is also the ability to embed in the opposite direction: that is, to

embed your warfile into the winstone JAR itself. This allows an all-in-one container plus

web-application JAR file to be downloaded, and then unpacked at execution time.

To use this, simply unpack the winstone JAR, and place your WAR file inside the unpacked

folder at the top level (with the same parent as the folder named "winstone"). Then rename

your WAR file to "embedded.war", and repack the jar as before (make sure to preserve the

META-INF and manifest).

Now if you type: <code>"java -jar winstone.jar"</code>, your application should

automatically deploy as the ROOT web application. Try <code>http://localhost:8080/</code> to

check it out.

If you need to add any default command-line arguments (eg ports or prefixes), you can embed

a properties file in exactly the same way, except that the file must be named

"embedded.properties".

%%

Thanks Matt, for this space and Rick Knowles for their attention and support on [Winstone|http://winstone.sourceforge.net/].

Raible's Wiki

AppFuse

Other Applications

AppFuseOnWinstone