Home >> All >> samples >> [ servlet Javadoc ]

•	samples.servlet.jsp.* (5)	•	samples.servlet.jsp.webform.* (5)	•	samples.servlet.xml.* (19)
•	samples.servlet.xml.login.* (9)	•	samples.servlet.xml.validation.* (5)	•	samples.servlet.xml.webform.* (5)

• samples.servlet: Javadoc index of package samples.servlet.


Package Samples:

• samples.servlet.jsp.webform
• samples.servlet.xml.login
• samples.servlet.xml.validation
• samples.servlet.xml.webform

Classes:

• ValidationModel: ValidationController uses one of these to supply data for its Views, and to keep session state in. It contains a number of properties, including a simple String, a Date that will involve a String conversion when the View repopulates its model, and a property that has a validation rule that may result in a thrown Exception. This model contains a list of String validation failures that are put in red at the top of the page. Scope's default ModelManager implementation builds on the JavaBeans API, so this model object is just a normal JavaBean.
• JSPFormModel: FormController uses one of these to supply data for its Views, and to keep session state in. In this case there's just a single String field that users populate with their name. Scope's default ModelManager implementation builds on the JavaBeans API, so this model object is just a normal JavaBean.
• FormModel: FormController uses one of these to supply data for its Views, and to keep session state in. In this case there's just a single String field that users populate with their name. Scope's default ModelManager implementation builds on the JavaBeans API, so this model object is just a normal JavaBean.
• FormModel: FormController uses one of these to supply data for its Views, and to keep session state in. In this case there's just a single String field that users populate with their name. Scope's default ModelManager implementation builds on the JavaBeans API, so this model object is just a normal JavaBean.
• LoginAppController: Top-most application Controller for the Login Sample, creates a child FormController, but handles the Login process itself so that any child Controller can do logins by passing a REQUEST_LOGIN Control up the chain of command.
• LoginManager: Session handling related to login. Simple impl with no roles etc: users are either logged in or not. Simple!
• LoginControls: Define the "RequestLogin" ControlID for use everywhere in the application.
• ValidationView1: ValidationView1 allows users to enter a String, a Date and an integer.
• ValidationView2: ValidationView2 shows the properties in the ValidationModel.
• JSPFormServlet: Override JSPScopeServlet to initialise application.
• ValidationServlet: Override XSLScopeServlet to initialise application.
• FormServlet: Override XSLScopeServlet to initialise application.
• JargusServlet: Html form servlet which uses PageBuilder to make html page.
• LoginAppServlet: Override ScopeServlet to initialise application.
• JSPFormView1: JSPFormView1 allows users to enter their name.
• FormView1: FormView1 allows users to enter their name.
• FormView1: FormView1 allows users to enter their name.
• HtmlFormValidationHandler: Html form implementation of a ValidationHandler.
• JSPFormView2: JSPFormView2 shows user name.
• FormView2: FormView2 shows user name.
• FormView2: FormView2 shows user name.
• PageBuilder: Create Output für Servlet.
• JSPFormController
• FormController
• LoginView

Home | Contact Us | Privacy Policy | Terms of Service