Here is an example from OzStruts sample application. VendorDetail.jsp has two
source pages, one is vendorSearch.jsp, and another is addVendor.jsp. In
addVendor.jsp to vendorDeatil.jsp transition, ActionForm must have properties to
get http request from addVendor.jsp, and rendering properties for vendorDeatil.jsp
and addVendor.jsp for error. Thus ActionForm will have properties for two pages.
On the other hand, the transition from vendorSearch.jsp is just http link with single
destination page, so ActionForm don’t have to consolidate properties for the two
pages. It looks hard for junior developers isn’t it?
***Are you saying that (in normal Struts) the "submit" button for vendorSearch.jsp and the "submit" button for addVendor.jsp both call the same Action (and the same ActionForm)?
Typically, each "submit" button calls a separate action. The struts manual says " Write an |Action| class for each logical request that may be received (extend |org.apache.struts.action.Action|).".
Bill
Tak Yoshida wrote:
Hi,
I would like to introduce Page Driven development, OzStruts, to all Struts developers, which makes Struts application more clean and maintainable.
I guess most of Struts developers are having same issues I had, so please take a look at my two cent idea. Any productive suggestion and critices would be really appreciated.
Documentations are available at http://sourceforge.net/project/showfiles.php?group_id=111296&package_id=120334&release_id=280886
OzStruts 1.0 is available at http://sourceforge.net/project/showfiles.php?group_id=111296&package_id=128965&release_id=280994
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
