OOP FormGenerator API : Simpler than JSP, JSTL, Apache Struts or JavaServer Faces / Input validation from CGI FORM / Easy localization (L10n) / Servlet in Japanese Shift_JIS, Chinese BIG5 or GB2312

Servlet by template XML. Simpler than JSP/JSTL, Apache Struts or JavaServer Faces. Input validation from CGI FORM. Localization (L10n). Servlet in Japanese Shift_JIS, Chinese BIG5 or GB2312.
In the framework design by OOP FormGenerator API, all the Servlet response can be written in the normal HTML or any other mark-up languages (such as XHTML, WML or HDML). Unlike the JSP/JSTL based solution such as Apache Struts or JavaServer Faces, the web designers (or page authors) need not learn a bit of the custom tag libraries.
This Java API makes the localization (L10n) of your Servlet much easier. In case of Apache Struts or JavaServer Faces, the localized messages should be written in the property resource file for the expected Locale. But, in this framework, what you need is to write the normal HTML for each expected Locale along with the localized messages. There is not difficulty even in the 2 bytes characters such as Japanese Shift_JIS, Chinese BIG5 or GB2312.
Once the HTML is prepared, the Java Swing GUI based conversion tool generates the XML. While in the conversion, you will be asked to specify the acceptable data type for each request parameter from the CGI FORM. Given this XML, a few lines of codes will be enough for the input validation in your Servlet.

To show you how to use this Java API, the following examples are running on our web site.

• The first example of OOP FormGenerator
• The second example of OOP FormGenerator

Related Pages:

• HtmlToXml Tutorial 1
• HtmlToXml Tutorial 2
• HtmlToXmlEdit Tutorial
• API documentation for OOP FormGenerator
• form_gen_2_0.dtd (DTD for OOP FormGenerator)
• OOP Distributor : ESD, Shopping Cart for digital goods by OOP-Research

This API is deprecated.

Please use OOP Bento Framework instead of this API. Within OOP Bento Framework, you can deploy all the existing XML for this API. This means that OOP Bento Framework takes over all the benefits of this API.

Servlet response by the normal HTML!

Believe or not, all the response from your Servlet can be written in just the normal HTML (or any mark-up languages such XHTML, WML or HDML)! Unlike the JSP/JSTL based solutions like Apache Struts or JavaServer Faces, the web designers (or page authors) of your project need not know even a bit of the custom tag libraries. Once the response is written in the normal HTML, it's time to run HtmlToXml conversion tool:

• (docBase)/WEB-INF/classes

    private static FormGenerator gen=null;

    public void init()
	throws ServletException{
	try{
	    gen=FormGenerator.getInstance();
	}
	catch(Exception ex){
	    ex.printStackTrace();
	    throw (new ServletException(ex));
	}
    }

    public void doGet(HttpServletRequest req, HttpServletResponse res)
	throws ServletException,IOException{

	try{
	    Form hello=gen.getForm("xml/hello.xml");
            hello.setDefaultValue("time",(new Date()).toString());
	    res.setContentType(hello.getContentType());
	    PrintWriter out=res.getWriter();
	    out.print(hello.getMerged());
	    gen.reuseForm(hello);
	    out.flush();
	    out.close();
	}
	catch(Exception ex){
	    throw (new ServletException(ex));
	}
    }

• (docBase)/WEB-INF/classes/xml/hello.xml

Input validation from CGI FORM by XML

While interacting with the user, each text field in your CGI FORM expects the specific pattern of input. For example, the user should type only the digit (0-9) in some text field of your CGI FORM. If s/he sends the wrong input, the destination Servlet should detect it and show the same CGI FORM again. But the CGI FORM at this time should include all the previous inputs in it as the default value. In addition, the wrong input should be indicated by the colored font or something:

• The first example of OOP FormGenerator
• The second example of OOP FormGenerator

Easy localization (L10n)

In case of the JSP/JSTL based solutions like Apache Struts or JavaServer Faces, the localized messages should be written in the property resource file for each Locale. In the template solution by OOP FormGenerator API, the localization (L10n) of your Servlet is much easier. Please prepare the normal HTML in as many human languages as you like (each of them will includes the localized message for the expected Locale). Because all the localized messages can written in the normal HTML, there is no difficulty even in the 2 byte characters such as Japanese Shift_JIS, Chinese BIG5 or GB2312.

Once you prepare the set of the HTML, please run HtmlToXml conversion tool on the HTML for each Locale. As a result, you will get the XML for each Locale. For example, your template XML will look like below:

• (docBase)/WEB-INF/classes/xml/hello_en.xml
• (docBase)/WEB-INF/classes/xml/hello_fr.xml
• (docBase)/WEB-INF/classes/xml/hello_de.xml
• (docBase)/WEB-INF/classes/xml/hello.xml

• The first example of OOP FormGenerator
• The second example of OOP FormGenerator

Performance improvement by pooling mechanism:

When the FormGenerator object reads the XML, all the information in the XML are cached in the pool. So, the same XML is read only once within the life cycle of the Servlet.
In addition, the FormGenerator object has the pool for the Form objects. Only if no free instance of Form is available in this pool, the new Form object will be created.

Download:

-- 90.00 USD with 1 year FREE upgrade
-- Or FREE 15 days trial

You can try or purchase this product at Java API Shop by OOP-Research.

• [Home]
• [SiteMap]
• [About Us]
• [Privacy Policy]
• [Contact Us]

• [How to upload file by JSP]
• [How to send e-mail by JSP]
• [JDBC PreparedStatement]
• [Shift_JIS/BIG5/GB2312]
• [Servlet by HTML]
• [Java Swing GUI]
• [JCE/RSA]
• [How to for Apache Tomcat]
• [How to for JOnAS EJB/Mysql]
• [Source code example]
• [Archives]
• [Reference]
• [Links]
• [Download]