Since JSF is *supposed* to replace Struts, so to speak,
This statement is *not* a correct understanding of what is happening! Anyone who claims that doesn't get it.
You should absolutely, positively plan on evaluating the use of JavaServer Faces components instead of the Struts HTML tags, and the JSTL tags instead of the corresponding bean and logic tags. Besides being standadized (which means, for example, that you can import and use *anyone's* JavaServer Faces tags, not be stuck with ones that are provided only by Struts), they are more powerful and more functional -- and they work fine in conjunction with Struts based applications.
That has nothing to do with whether or not you need the other features of Struts (the core controller mechanisms, plugins, Tiles, Validator, ...) -- which can be used just fine with JavaServer Faces components as well. There is a functionality overlap in the core controller role, and for some people JavaServer Faces will be sufficient by itself. But it's our job as Struts developers to ensure that the gap continues to exist and increases; there's a lot of things required to build good web apps that are not UI components or tags, and are therefore outside the scope of JavaServer Faces and JSTL.
Craig McClanahan
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
