 | Mailing List | | Home | | Forum Home | | JBoss - Java Application Server | | Struts - A MVC web framework | | Tomcat - JSP/Servlet container | | iText - An open source PDF Java Library | | JDOM - JDOM XML Parser | | J2EE - A mailing list for Java(tm) 2 Platform, Enterprise Edition | | J2EE Pattern - An interest list for Sun Java Center J2EE Pattern Catalog | | Servlet - A mailing list for discussion about Sun Microsystem's Java Servlet API Technology | | JSP - A mailing list about Java Server Pages specification and reference | |
Struts & Hibernate
|
|
|
| | | Workflow logic handling and "go back " handling | Workflow logic handling and "go back " handling 2003-07-07 - By Jeff Jensen
Back
Hi,
We are starting to design a new web app that has lots of workflow logic. We
are using Struts for the controller and front flow control. We have the option
to use most any J2EE technology.
The workflow logic is complex. The system involves many screens of
user input, and the screens presented change depending on user-entered choices.
The decision-logic for "where to go next" not only involves the data from the
screen just visited, but often also from prior screens.
None of us have experience with a larger and more complex decision tree logic
like this. A couple of us have done something on a much smaller scale, and
fear that ideas in that context do not apply/scale/work well in this one.
Another wrinkle is the requirement to allow the user to go back to previous
screens and change anything. This of course affects a lot of things, including
how to determine what data to discard with a change by the user that affects
the decision tree/screens presented.
So, besides "put the logic in session beans/facades", we need lots of advice on
how to solve these two main problems!
Are there any patterns/pattern languages to consider? Are there any open
source libs/products to assist? Is there a good architecture for this to
minimize having a plethora of code in session beans to determine the next
view?
My guess is many teams must have already solved these problems; I know this is
not "new"! Can anyone shed some light on best-practice solutions please?
I would appreciate any pointers and/or redirects to help solve the problem.
Thank you!
====================================================================
Community Web Site (Core J2EE Patterns Catalog - Online Version):
http://java.sun.com/blueprints/corej2eepatterns
Getting Started (Beta Version):
http://developer.java.sun.com/developer/technicalArticles/J2EE/patterns/
Get the book:
http://www.amazon.com/exec/obidos/ASIN/0130648841/corej2eepatte-20 (See http://tte-20.ora-code.com)
List Archive:
http://archives.java.sun.com/archives/j2eepatterns-interest.html
Unsubscribing:
email "signoff J2EEPATTERNS-INTEREST" to listserv@(protected)
|
|
|
