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?
Hmmm, you're mostly right, except for Wicket where there really is no
overhead it seems. They just instantiate a new component. No
configuration is needed for that, so there are less steps and less
files. My problem with that is that it might seem nice in small
example applications. I find it already confusing when looking at
some of their larger examples since you really have to read all the
code to know how everything relates.
--
Geert Bevin
Uwyn "Use what you need" - http://uwyn.com
RIFE Java application framework - http://rifers.org
Music and words - http://gbevin.com
_______________________________________________
Rife-users mailing list
[email protected]
http://lists.uwyn.com/mailman/listinfo/rife-users
