Struts dynamic form application

This article explains the reference of DynaForms in Struts1.1 in instance code - Translator Note

If you have used Struts Previous versions, you will notice that you need to spend a lot of time to write an actionform class file, and these types of files are very critical for Struts (it acts as part of "View"), usually it The structure is Bean Properties plus a validate method (sometimes reset method).

With the launch of the Struts1.1, the developer has another way to complete the previous tasks: use Dynabeans. Dynabeans dynamically generate Java Beans. This means that we can configure (usually using XML)

To generate FormBean instead of hard coding in FormBean.

To learn how Dynabeans (Struts is DynaForms), let's take a simple form, the fields are: Name, Address, Telephone, etc., the following code is the usual way of writing (not using DynaForms).

Article1.customerform

Package article1;

Import org.apache.struts.Action.actionform;

Import org.apache.struts.Action.Actionerro;

Import org.apache.struts.action.actionmapping;

Import org.apache.struts.Action.Actionerror;

Import javax.servlet.http.httpservletRequest;

Public class customerform extends actionform {

Protected Boolean NullorBlank (String Str) {

Return ((Str == Null) || (str.length () == 0));

}

Public ActionerRors Validate (ActionMapping Mapping,

HttpservletRequest request) {

ActionerroS Errors = new actionerrors ();

IF (NullorBlank (Lastname)) {

Errors.Add ("lastname",

New Actionerror ("Article1.lastname.Missing")));

}

IF (nullorblank (firstname)) {

Errors.Add ("firstname",

New ActionError ("Article1.Firstname.Missing")));

}

IF (Nulloblank (Street) {

Errors.Add ("street",

New ActionError ("Article1.street.Missing");

}

IF (nullorblank (city) {

Errors.Add ("City",

New Actionerror ("Article1.city.Missing"));

}

IF (nullorblank (state)) {

Errors.Add ("State",

New Actionerror ("Article1.State.Missing");

}

IF (NullorBlank (Postalcode)) {

Errors.add ("Postalcode", New Actionerror ("Article1.Postalcode.Missing");

}

IF (NullorBlank (Phone)) {

Errors.Add ("Phone",

New ActionError ("Article1.Phone.Missing"));

}

Return Errors;

}

PRIVATE STRING LASTNAME;

Private string dimstname;

PRIVATE STRING STREET;

PRIVATE STRING CITY;

PRIVATE STRING State;

PRIVATE STRING POSTALCODE;

PRIVATE STRING

Public string getlastname () {

Return Lastname;

}

Public void setlastname (String lastname) {

THIS.LASTNAME = LastName;

}

Public string getFirstName () {

Return firstname;

}

Public void setfirstname (String firstname) {

THIS.FIRSTNAME = firstName;

}

Public string getStreet () {

Return street;

}

Public void setstreet (String Street) {

THIS.STREET = STREET;

}

Public string getcity () {

Return city;

}

Public void setcity (string city) {

THIS.CITY = CITY;

}

Public string getState () {

Return State;

}

Public void setState (string state) {

THIS.STATE = State;

}

Public string getpostalcode () {

Return Postalcode;

}

Public void setPostalcode (String Postalcode) {

THIS.POSTALCODE = Postalcode;

}

Public String getphone () {

Return Phone;

}

Public void setphone (string phone) {

This.Phone = Phone;

}

}

Seeing the next way (such a long code [Although most of the tools can automatically generate set and get methods]? If you want to match a FORMBEAN for each form, you will be a more painful thing - - Translator's Note), you know that it is a standard JavaBean, just a validate method, the Validate method ensures that the Client break is legal.

The corresponding JSP page is also very simple, as follows:

Customer.jsp

<% @ Taglib Uri = "/ Web-INF / C.TLD" prefix = "c"%>

<% @ taglib prefix = "FMT" URI = "/ Web-INF / FMT.TLD"%>

<% @ Taglib Uri = "/ Web-INF / STRUTS-TILES.TLD" prefix = "tiles"%> <% @ Taglib URI = "/ Web-INF / STRUTS-HTML.TLD" prefix = "html"%>