<http://jakarta.apache.org/struts/status.html>
It's important to note that the tags have always been a extension of the core framework. The framework originally shipped with a custom tag library, because that's what people needed most. Since then, support for many other display technologies have been added, including JSTL and JSF, as well as XLST and Velocity. For some time, we have been emphasizing that Struts is a Controller framework that supports various presentation layers.
I'm sure many Struts developers will start using JSF, once the specification is finalized and implementations are available -- just as many Struts developers are using JSTL today. (While even others use XLST, Velocity, and so forth.) For the most part, Struts and JSF are complementary. Struts provides a flexible, pluggable request processor. JSF provides a rules-based navigational system. Some teams may be able to JSF rules that instead of the Struts Controller, others might use the Struts controller with JSF tags, or perhaps one for this workflow and another for that workflow. It's not an election of remedies. There are a lot of gaps in JSF (as well as in Struts 1.1) that can be filled by standard, open-source extensions maintained by projects like this one.
If you plan to use JSP tags, and can use Servlet 2.3/JSP 1.2, the best longterm JSP tag strategy right now would be to go with JSTL. The conventional tags will be supported so long as someone volunteers to do the work, but no one seems to be stepping forward. However, tens of thousands of applications have shipped with the original tags, so they must be doing something right =:0)
But, the thing with a project like Struts, is that it's not about planning. It's about doing. The future of Struts lies in the hands of people who contribute to the codebase and "make it so".
-Ted.
Marco Tedone wrote:
Hi, is now the future of Struts the integration with JSF and JSTL? Does it mean that Struts will be only a background framework leaving the presentation (HTML, JSP) to JSF and JSTL? Is Sun going to open a new project to build a background framework (a sort of Sun-Struts)?
In this case I wouldn't say that this would be bad (maybe on the opposite!) but I would like to know it to take strategic decisions for my projects.
Marco
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Ted Husted, Junit in Action - <http://www.manning.com/massol/>, Struts in Action - <http://husted.com/struts/book.html>, JSP Site Design - <http://www.amazon.com/exec/obidos/ISBN=1861005512>.
"Get Ready, We're Moving Out!!" - <http://www.clark04.com>
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
