Originally posted by raj sekhar:
Hasnt JSTL taken so much time (due to JSR or anyother reason) to come out? Meanwhile most of the dev community has already started Jakarta taglibs/ struts or custom taglibs. With introduction of JSTL at this point, does changing to JSTL provide clear advantage ? Does the return on investment(in terms of time and effort) supported ?
I think that in general, JSTL came out at the right time; earlier on, we didn't have enough experience to know what to standardize. Now, the consensus seems to be that the standard covers, in general, what it's supposed to cover.
Note that JSTL is not an alternative to Struts or Jakarta Taglibs; all of these projects are complementary with one another. Struts is primarily a framework for developing controllers; its presentation-tier taglibs will be replaced with JSTL's eventually. JSTL supercedes some of Jakarta Taglibs (particularly the "page," "request," "session," and "application" taglibs -- and similar ones), but the other areas covered by Jakarta Taglibs do not overlap with JSTL. The goal is still for Jakarta Taglibs to be more experimental than JSTL and thus reach further into areas that need not yet be standardized.
Thus, you're not faced with a choice between JSTL on the one hand and other technologies on the other. JSTL successfully integrates with Struts, Jakarta Taglibs, and JavaServer Faces.