Action classes represent the "controller" part of Struts, and the "controller" part of the MVC pattern controls things. It does things. Yes, that's right, the Action class is where the money's at, yo, because once a user presses a button on a page, it's up to an Action class to respond to it and make something happen.
Table of Contents |
---|
Extending org.kuali.
...
kfs.kns.web.struts.action.KualiTransactionalDocumentActionBase
Anchor | ||||
---|---|---|---|---|
|
For our own document's actions, we need to extend org.kuali.rice.kns.web.struts.action.KualiTransactionalDocumentActionBase or a descendant class. Again, the rules about parallel hierarchies are also in effect here. The class should be named {transactional document name}Action and should live in the org.kuali.kfs.module.{the module we're working in}.web.struts package.
...
KualiDocumentActionBase also has methods to handle adding and deleting ad hoc routing and the adding or deleting of notes and attachments. There are only two action methods defined in org.kuali.ricekfs.kns.web.struts.action.KualiTransactionalDocumentActionBase:
...
Code Block | ||||
---|---|---|---|---|
| ||||
<form-bean name="KualiForm" type="org.kuali.ricekfs.kns.web.struts.form.KualiForm" /> <action path="/portal" name="KualiForm" type="org.kuali.ricekfs.kns.web.struts.action.KualiSimpleAction"> <forward name="basic" path="/portal.jsp" /> </action> |
...