java.lang.Object
org.apache.struts.action.ActionForm
com.obs.webapp.struts.form.CreateAccountForm
- All Implemented Interfaces:
- java.io.Serializable
- public class CreateAccountForm
- extends org.apache.struts.action.ActionForm
| Methods inherited from class java.lang.Object |
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
accountID
private java.lang.String accountID
accountName
private java.lang.String accountName
balance
private java.lang.Double balance
active
private java.lang.Boolean active
accountType
private java.lang.Integer accountType
CreateAccountForm
public CreateAccountForm()
validate
public org.apache.struts.action.ActionErrors validate(org.apache.struts.action.ActionMapping mapping,
javax.servlet.http.HttpServletRequest request)
- Method validate
getAccountID
public java.lang.String getAccountID()
getAccountName
public java.lang.String getAccountName()
getAccountType
public java.lang.Integer getAccountType()
getActive
public java.lang.Boolean getActive()
getBalance
public java.lang.Double getBalance()
setAccountID
public void setAccountID(java.lang.String string)
setAccountName
public void setAccountName(java.lang.String string)
setAccountType
public void setAccountType(java.lang.Integer integer)
setActive
public void setActive(java.lang.Boolean boolean1)
setBalance
public void setBalance(java.lang.Double double1)
getViewObject
public com.obs.common.templates.ViewObject getViewObject()
setViewObject
public void setViewObject(com.obs.common.templates.ViewObject view)
reset
public void reset(org.apache.struts.action.ActionMapping mapping,
javax.servlet.http.HttpServletRequest request)
- Description copied from class:
org.apache.struts.action.ActionForm
Reset bean properties to their default state, as needed. This method is
called before the properties are repopulated by the controller.
The default implementation does nothing. In practice, the only properties
that need to be reset are those which represent checkboxes on a session-scoped
form. Otherwise, properties can be given initial values where the field is
declared.
If the form is stored in session-scope so that values can be collected
over multiple requests (a "wizard"), you must be very careful of which
properties, if any, are reset. As mentioned, session-scope checkboxes
must be reset to false for any page where this property is set. This is
because the client does not submit a checkbox value when it is clear (false).
If a session-scoped checkbox is not proactively reset, it can never be set
to false.
This method is not the appropriate place to initialize
form value for an "update" type page (this should be done in a setup Action).
You mainly need to worry about setting checkbox values to false; most of the
time you can leave this method unimplemented.