| Raible's Wiki
    Raible Designs AppFuseHomepage- Korean - Chinese - Italian - Japanese QuickStart Guide User Guide Tutorials Other ApplicationsStruts ResumeSecurity Example Struts Menu 
 
    
    
         
        Set your name in UserPreferences 
 
 Referenced by 
   JSPWiki v2.2.33 
    
 Hide Menu | 
 
      
         
      
      
         
             This is version 25.  
            It is not the current version, and thus it cannot be edited. This page describes the steps to get AppFuse 1.9 working on Winstone  . Sincerely a simply and at the same time powerful container. 
Have you tried to install an appfuse project as a desktop application? No! Now you can do it! How?
Let's see how is simple to make AppFuse run on Winstone  : 1. Build AppFuse as usual (project name: felini): ant war; 2. Create a directory, for example, felini and on it a sub-directory: lib; 3. Download Winstone 4. Copy your war file to felini and copy your JBDC Driver and jta.jar to lib directory; 5. Other thing, in order to turn on JSP compilation in Winstone 6. From the felini directory run: java -jar winstone-0.8.1.jar --warfile=feline.war --useJasper That's it! No more no less! But wait, it has more ...NOTE: This is from Winstone docs: Embedding WinstoneThe design of Winstone has always allowed its easy embedding within another application. It's as simple as:  // 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
 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:  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 
 | ||||||