Contents

Code Generation from the CALM Form Editor ( for Struts Framework)

Once you had associated all the assessment scores and the mandatory fields with the form components, it is time to generate the JSPs, Struts Form Bean and update the struts-config.xml file for the Generic Assessment Management Engine (GAME) in the HID web application. For this, select Struts Code Generator from the Tools menu. You will see the following dialog box;

This the only mandatory information that needs to supplied for the Struts JSP, FormBean Java code generation and update of the struts configuation file template. Here you specify the location of the HID web application as checked out from the BIRN CVS repository.
After that, you will see the following dialog box with all fields completed using the Clinical web application Home directory info just
supplied.

Application Context: The J2EE web application context name for the HID web application. The default is fine for almost all cases.
Package Name - default is fine for almost all cases
Form Bean Name - The name of the Struts form bean that will be generated
Form Bean ID - a logical name for the Struts form bean. It is mainly used in form-bean declaration in struts-config.xml.template

        <form-bean name="qmForm"
          type="clinical.web.game.forms.QuickMoodForm"/>
Source Code Root - the directory where your HID web application source code tree is located
JSP Code Root - the directory where the generated JSP pages will end up.
Stuts Config File Path - the path for your HID web application struts-config.xml.template file. CALM form editor updates this file to add the necessary actions and form bean declaration for the generated JSPs.
Generated Code Directory - the directory where CALM editor saves the intermediate files (XForms 1.0 compliant XML files and XSL style sheets used to transform the XForms forms into the corresponding JSPs.
Struts Action Prefix - the static part of the Struts action path attribute in the generated action tag in the struts-config.xml.template.

Relative JSP Path - the default is OK with almost all cases

Since each clinical assessment can map to multiple JSPs, the names of the to be generated JSPs must be specified. CALM form editor gives them default names.

The initial values are good for almost all cases, you can always edit these values. Next, press OK to start code generation.