GET STARTED

1. build the business.jar using the business.zip and ant
2. place the business.jar in the joinStruts lib directory
3. place a recent copy of struts.jar (and *.tld) files into lib directory
4. build
5. place resulting war file into Tomcat/webapps folder

----------------------------------------------------------------------

joinStruts PROJECT STRUCTURE:

lib - 3rd party libs such as business.jar and struts.jar

src - source code

web - web project that would normally go into a Tomcat project

build.xml - builds the joinStruts.war that is deployable to Tomcat

build - created by ant during the build process


----------------------------------------------------------------------

RESULT OF BUILD PROCESS

joinStruts.war web archive (WAR) structure

join.jsp - old/bad style jsp

joinMVC.jsp - new improved style jsp

web-inf:
    app.tld - The application tag library. This is where you would place 
	      tags specific to your application.

    action.xml - Action mappings for the web application. This file determines 
                 the flow of the application.  Notice that this is static file 
                 and not dynamic.  This might affect your application design if your
                product is worked flow baseds. (limit your application if it is workflow based).

    struts.tld - this is the tag difintions for the STRUTS Framework Tag Library

    struts-bean.tld - Struts Bean/Property Tags definitions - 
        A set of classes used to access beans and their properties.

    struts-logic.tld - Struts Logic Tags defintions - 
        The logic library contains tags that are useful in conditional output generation.  

    web.xml - j2ee web project configuration file.

    lib
        struts.jar - 

        business.jar - 
            the business package for project.  I don't have to put this jar file here.  
            I could put it in my path, but I prefer to put it here to keep the 
            path simple.  Second, development of business could happen independent 
            of the website.  And last, it's a reminder of what I need to ship with the 
            website when it goes into production and avoids conflicts with other versions of   
            business.jar

