The first concrete example of mapping action "status/result" to destination
was given by Daniel to my recollection. It was part of his webleaf project.
There was mention also of a "state-machine" approach.
I prefer the "state-machine" approach for my specific application.
I deal with leasing systems and there is a re-entrant workflow that needs to
be modeled.
I assign a lease a code for each major step in the workflow ( "customer
details received", "credit approved", "documents sent" and so on).
Each step has a next logical requirement so I like to push the lease reps
onto the most appropriate screen when they load a deal. In other words if
the lease is waiting for documents to be produced the "Produce documents"
screen should be displayed if that lease is selected from the work queue.
Anyway, without boring everyone with the tedium of leasing, the point is
that a mapping of "status" to UI page intersects nicely with the Model 2
stuff espoused by the group on this list that make it worth subscribing to
(they know who they are..and thanks to them all for their insight).
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
Some relevant FAQs on JSP/Servlets can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
