Hi Geert, > Thanks for the example though, it's a nice and clear one.
Glad to hear it :-) > Well, other frameworks have solutions for that too. In Wicket you > just create a new instance of a component, in Spring Web Flow you > return any object from your execution method and redirect the flow > based on an introspection of that, in WebWork you return a result > identifier that you tied to a next step in your navigation setup, ... Exactly. So why do people tell you that this is a burden in RIFE? If it's a burden in RIFE then it's a burden in the other frameworks too. Each framework has its way of doing it, and I don't understand why any of these ways is more or less of a burden than any of the other ways. I mean, in any case, you have to somehow associate a "successful result" to the next step. Did I miss something? Frederic _______________________________________________ Rife-users mailing list [email protected] http://lists.uwyn.com/mailman/listinfo/rife-users
