> * I could read from the database in the first Action > (delegate to some business class hopefully!) and stick it > directly in Request. But that breaks isolation between the > pages. The Action associated with one page should not set up > for another.
One thing I don't understand... The actions and the jsps are already connected to each other by the use-case and the requirement that the second action/jsp depends on the first. The use case could even go so far, that the first action have to decide whether to show the second action at all dependent on what the user entered there, right (Like in do you want additional insurance contract when you buy a car)? Or it could decide whether to forward to action 2a or action 2b and therefore influence the flow of events in this use case. What I don't understand is, why we should isolate two actions, which are tied to each other by definition? I think a wizard, and we are talking about wizards, as Rick explained in his mail, which was much better phrased as mine, is not only a collection of forms, but also the flow of control inbetween the forms. Why should I break this natural dependency? Regards Leon --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
