On 6/8/06, Craig McClanahan <[EMAIL PROTECTED]> wrote:
On 6/8/06, Frank W. Zammetti <[EMAIL PROTECTED]> wrote:
* Annotations are not a good idea when the configuration concept should not be a concern of the person actually writing the code. In webapps, for example, I don't believe in configuring page navigation rules (Struts forwards, JSF navigation rules and cases, etc) directly into the action methods. The actions should describe what happened, not where to go next -- and this is something I personally don't care for, even at the code level, the way that WW2 does Results (or Spring MVC does ModelAndView) that combine the two concerns together. But that's a separate issue from whether the encoding should be with annotations or not :-).
I don't think that framework should define the navigation at all. Well, maybe in some specific cases like redirecting a non-logged-in user to a login page. But generally, a user navigates to a certain resource himself by clicking links. Resources have states; depending on state they render themselves differently, but this is not navigation, this is just views/subviews. Programmatic navigation seems like a wrong concept altogether to me. Michael. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
