MVC vs. WebLogic, beehive, pollinate, JSF?
I was glancing some descriptions of the above technologies and one thing that surprised me was that after profound talks about MVC pattern all the authors seem to switch to specifying the workflow as a page flow. Litteraly the use cases are described like this (in JSF):
<navigation-rule>
<from-view-id>/pages/inputname.jsp</fr
<navigation-case>
<from-outcome>sayHello</from-outcome>
<to-view-id>/pages/greeting.jsp</to-vi
</navigation-case>
<navigation-case>
<from-outcome>sayGoodbye</from-outcome>
<to-view-id>/pages/goodbye.jsp</to-vie
</navigation-case>
</navigation-rule>
I naively thought that the execution control should be done by the controller, and it is baaad to model it as the links in the presentation layer. Am I wrong, or everybody is blind?
<navigation-rule>
<from-view-id>/pages/inputname.jsp</fr
<navigation-case>
<from-outcome>sayHello</from-outcome>
<to-view-id>/pages/greeting.jsp</to-vi
</navigation-case>
<navigation-case>
<from-outcome>sayGoodbye</from-outcome>
<to-view-id>/pages/goodbye.jsp</to-vie
</navigation-case>
</navigation-rule>
I naively thought that the execution control should be done by the controller, and it is baaad to model it as the links in the presentation layer. Am I wrong, or everybody is blind?
