You are right, JSTL doesn't completely remove the need for Struts specific
tags.

I think for the purposes of this discussion, the "next generation" would be
JSTL plus the struts-el taglib and when we talk about the Struts tags, we're
really talking about the traditional, non-el tags.

So keep using the <html:form> and other Struts tag and consider migrating to
the EL versions if you are using JSTL.

Steve


> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: September 1, 2003 1:17 AM
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: RE: Support for non-JSTL tags (was RE: DO NOT REPLY [Bug 21465]
> - Enhancement of the html:link tag)
>
>
> Perhaps this belongs on the user list, but I think it is relevant for
> the discussion at hand. You all seem to regard all of the Struts taglibs
> as one item, for which JSTL is an alternative. While this is certainly
> true for the logic: and bean: tags, I have not seen a replacement for
> the
> html: form tags (that is, <html:form> and all the controls) in JSTL.
>
> The user guide
> (http://jakarta.apache.org/struts/userGuide/building_view.html#form_bean
> s)
> suggests we replace
>
> <input type="text" name="username"
>        value="<%= loginBean.getUsername() >"/>
>
> with
>
> <html:text property="username"/>
>
> Does the "use JSTL" camp prefer this,
>
> <input type="text" name="username"
>        value="<c:out value="${loginBean.username}"/>">
>
> or am I missing some basic JSTL?
>
> Shai.
>
>
> PS: There is a documentation error there; the original JSP should be
>
> <input type="text" name="username"
>        value="<%= loginBean.getUsername() %>"/>
> ------------------------------------------^
>
> Shai.
>
>
> ---
> Confidentiality Notice: This email transmission may contain
> confidential or legally privileged information that is intended
> only for the individual or entity named in the e-mail address. If
> you are not the intended recipient, you are hereby notified that
> any disclosure, copying, distribution, or reliance upon the
> contents of this e-mail is strictly prohibited. If you have
> received this e-mail transmission in error, please reply to the
> sender, so that arrangements can be made for proper delivery, and
> then please delete the message from your inbox.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to