Doesn’t it seem like we deal with this all the time? We need to design for the case where we use a page for multiple purposes, which means that on Submit and Cancel we will need to go to different place depending on where we came from.
This thread gives some ideas for solving this that are in no way satisfying.
http://www.mail-archive.com/struts-user@jakarta.apache.org/msg25193.html
Let’s come up with a design pattern for this that we will all use from the get-go on future projects. That way we can avoid shoehorning a complex solution into existing code at end of a project.
Tags: design patterns, struts, workflow
