Hubert Rabago wrote:
I haven't finished exploring all of the nav features of JSF, but I tend to agree with this comment. Navigation seems to me to be one of the more awkward aspects of Struts. I came up with my own navigation solution to put on top of Struts when I had multi screen wizards that needed to have "next" and "prev" buttons (and also reused screens.) I could probably dump this in favor of JSF.Yes. Some even believe the navigation rules of JSF is easier to understand than those of Struts.
The navigation of JSF also seems to be a big reason why you wouldn't want to use both Struts and JSF together indefinitely. I think it would get confusing having 50% of the navigation rules contained in the struts-config and 50% in the faces-config.
Are the UI widgets of JSF really that compelling? So far I think there are some minor improvements over Struts tags but the real promise seems to be in third party/open-source add-ons which are in the infancy stages. Plus the UI widgets often require preprocessing to use. At that point it seems like why not just go with JSF completely?You could use both if you had no plans of switching fully but would like to take advantage of the UI widgets of JSF.
I don't have anything against JSF as a whole, but a lot of times II agree. That's why I want to discuss with others and think it through carefully. So far my plan is to evaluate JSF fully and decide whether I like it better than Struts (in its current inception with the currently available tags) . I know its not completely an "either-or" decision but I'd rather minimize the mixing of the two frameworks as much as possible.
feel like most switchers are switching just because they feel that
other people are switching, too.
My two cents.
sean
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
