JSP screens at runtime

Question

how can i create JSP screens at runtime with just an XML file. this is my project for the college. actually i'm new to jsp and xml. i've got a mail which was sent by the guide to me. if u can understand what they are trying to explain, then plz help me out.
following is the description of my project as given by my guide.
Framework is designed to customize user needs in Less programming time and deliver with standard. Any Web based enterprise project requires maintenance of masters. These Operations at times have no business logic. Framework deals with such type of operations creating screens for programmer with just an XML file.
In Framework request in the form of parameter is sent to Centralized Servlet.
<< Mention entries in web.xml >>
Servlet reads the value of parameter by name "command". Servlet identifies the command and gets the respective handler and process the request in handler. A Handler is skeletal for servlet, which process the required logic for respective command. Handler helps in forwarding the request to another jsp through Servlet��s Request Dispatcher
The below points can help u all in devloping the project, I mean the format and tags etc. Use this as the basis and try to search in the net to explore more on XML and develop u'r project.
The XML file format is as follows:
1. XML file.
XML file name should be same as table name.
For Eg:- If master maintenance screen has to be created for the table coursemaster, then the XML file name should be coursemaster.xml
2. XML file structure.
It has starting node by name Root. Which indicates parent node.
<Root type = "ca" >
Next specifies the child node under Root, which should be similar to the XML file name.
<coursemaster type = "cp" >
To specify the user-friendly module name, which can be displayed in UI screen. You need to use
<Module name="coursemaster" col="2" />
Note:
The value, which you specify under name attribute, should be the value that is present in language properties file, which helps in displaying the heading in respective languages like German, English, Korean etc.
The attribute col="2" specifies number of columns that the screen should display UI controls. The value specified should be only multiples of 2, i.e. 2,4,6,8 etc.
All the field names , the order in which they occur, and fields used to list on screen for search page should be specified between <Attribute></Attribute> nodes.
To specify order of controls that should occur on screen.
<Order value="vccourseid,vccoursename,vcduration,vccredits,ifee" />
Note:
Fieldnames are separated by commas.(These are the fieldnames present in table)
There should not be space between a comma and fieldname.
To specify fields for querying.
<QryResAttrs value="vccompanycode,vcunitcode,vcitemcode,dtvalidfrom,dtvalidupto" />
Note:
Here the fields, which are keys, and the fields, which are required through out the module, should be specified. First half should contain keys and then followed by fieldname for the rest of module.
To specify type of controls for all fields and there property.
The control properties are specified in <Attr> node with following attributes to specify properties.
Name �� Value should be similar to fieldname in table and one of the attribute in Order node.
Label �� Used to represent label on the screen, should be present in language properties file.
Display �� control type, the following list of controls are present in e-easy framework.
Design Algorithm:
Step 1: In ��Framework��, request in the form of parameter is sent to Centralized Servlet.
Step 2: The Servlet reads the value of parameter by the name ��command��.
Step3: Servlet identifies the command and gets the respective handler and processes the request in handler.
Step 4: Handler helps in forwarding the request to another JSP through Servlets Request Dispatcher.
As soon as Servlet reads the parameter value for ��command��, it accesses AppMap.xml, which stores all information about command values, the respective handler and JSPs. The java class, which reads the contents of AppMap.xml and gets respective information through meaningful methods, is ApplicationMap.class. The structure of AppMap.xml is as follows.
<command handler= ��handler_name�� jsp= ��JSPname.jsp��>
The JSPs used in ��The Framework��:
As the Controls are unknown, Display is unknown; Jsps puts the task to Tag Libraries to create Body for the jsps.
When a request is forwarded to jsp, the jsp executes the TagLibrary present in it. Tag libraries are present in taglib folder in Web-Inf directory as reports.tld file.
Class files for Respective Tag libraries and their actions.
To provide heading to JSP page table.
TagLibrary name is heading.
Java file is com.ample.tag.FormHead.java
<tag>
<name>heading</name>
<tagclass>com.ample.tag.FormHead</tagclass>
<info> Tag for displaying form </info>
</tag>
To provide title to JSP page.
<tag>
<name>title</name>
<tagclass>com.ample.tag.FormTitle</tagclass>
<info> Tag for displaying title </info>
</tag>
To generate Body for JSP with Controls depending on particular table in database:
<tag>
<name>form</name>
<tagclass>com.ample.tag.FormTag</tagclass>
<info> Tag for displaying form </info>
</tag>
To generate label for jsp Controls depending on particular table in database:
<tag>
<name>label</name>
<tagclass>com.ample.tag.FormLabel</tagclass>
<info> Tag for displaying label</info>
</tag>
For example displaying ADD page, to add a record to database.
All Form actions are carried out by tag library ��form�� which calls com.ample.tag.FormTag. Depending on ��command�� from servlet, respective jsps are displayed, which goes to FormTag with body message. In this case, Command=��create�� body message = CRE_USR . FormTag will read this message, and calls respective method to perform the task. The method reads the xml content with all specifications, and generates page writing back to page context of jsp.
Xml file for coursemaster.xml
<?xml version="1.0" ?>
<Root type="ca">
<coursemaster type="cp">
<Module name="coursemaster" col="2" />
<Key name="vccourseid" type="general" />
<Attribute>
<Order value="vccourseid,vccoursename,vcduration,vccredits,ifee" />
<QryResAttrs value="vccourseid,vccoursename,ifee" />
In the xml file, Query Attributes are
<QryResAttrs value="vccourseid, vccoursename, ifee" />
<Attr name="vccourseid" label="courseid" display="text" type="rp" format="String" width="24" table="coursemaster" read="+" write="+" update="-" query="+" jsfunc="isAlphanumeric" errmessage="Should be a String" align="right" />
<Attr name="vccoursename" label="coursename" display="text" type="rp" format="String" width="24" table="coursemaster" read="+" write="+" update="+" query="+" jsfunc="isAlphanumeric" errmessage="Should be a String" align="center" />
<Attr name="vcduration" label="duration" display="text" type="rp" format="String" width="24" table="coursemaster" read="+" write="+" update="+" query="+" jsfunc="isAlphanumeric" errmessage="Should be a String" align="center" />
<Attr name="vccredits" label="credits" display="text" type="p" format="String" width="24" table="coursemaster" read="+" write="+" update="+" query="+" jsfunc="isAlphanumeric" errmessage="Should be a String" align="center" />
<Attr name="ifee" label="fee" display="text" type="p" format="integer" width="24" table="coursemaster" read="+" write="+" update="+" query="+" align="center" jsfunc="isInteger" errmessage="Should be a Integer" />
</Attribute>
</coursemaster>
</Root>

Answer 1

Could it be that your import should state the package only, and not the class and therefore your're confusing the compiler?
Example:
From:
<%@ page import="com.aquitecintl.procurement.item.SCItemCopyApp" %>
<jsp:useBean id="iCpy" type="com.aquitecintl.procurement.item.SCItemCopyApp" scope="session" />
To:
<%@ page import="com.aquitecintl.procurement.item.*" %>
<jsp:useBean id="iCpy" type="com.aquitecintl.procurement.item.SCItemCopyApp" scope="session" />