Karr I did as per your explanation. This is the result: if you look at my success.jsp page, I had to use core_rt in the uri to get the output. If I use just core in the uri, I get an error as: "According to TLD or attribute directive in tag file, attribute value does not accept any expressions"
<!-- myjsppage.jsp --> <%@ taglib uri="http://java.sun.com/jstl/core_rt"; prefix="c" %> <html> <head> <title>jauth Application</title> </head> <body> The User Entering the application is : <c:out value="${data.name}" /> </body> </html> Why do I need to use core_rt and not core. I think core_rt is for JSTL 1.0 and not 1.1 ? Any ideas? ----- Original Message ----- From: "Karr, David" <[EMAIL PROTECTED]> To: "Struts Users Mailing List" <[EMAIL PROTECTED]> Sent: Thursday, October 14, 2004 7:03 PM Subject: RE: Using JSTL 1.1 with Struts 1.2.4 and JBoss 3.2.5 or 4.0? > -----Original Message----- > From: Satish Talim [mailto:[EMAIL PROTECTED] > > However, I am still unclear. Karr mentioned "The features > provided by Struts-EL are all natively provided in the > container. " - so how does this JBoss container evaluate > <c:out tag (if used) when there is no c.tld or the required > jar file? Any ideas? Sorry, I was unclear. What JSP 2.0 provides is native evaluation of EL expressions (and many other things). It does not directly provide the JSTL. So, if you want to use the EL with Struts in a JSP 2.0 container, just use Struts, not Struts-EL. You'll be able to use the EL in Struts tag attributes. If you want to also use the JSTL in this environment, use the JSTL 1.1. Just put "jstl.jar" and "standard.jar" in WEB-INF/lib, and use the "taglib" directive in your JSP pages. You don't need to extract the TLD files, and you don't need to specify the taglib in your web.xml. > ----- Original Message ----- > From: "Rick Reumann" <[EMAIL PROTECTED]> > > A much more important question is why are you doing this db > stuff in your JSP! > > Satish Talim wrote the following on 10/13/2004 2:00 AM: > > I am using JBoss 4.0 (which I believe is a Servlet 2.4 / JSP 2.0 > container) and Struts 1.2.4. > > > > I want to use JSTL 1.1 with Struts and JBoss. For example, I would > > like to > use something like this: > > > > <%@ taglib prefix="c" > uri="http://java.sun.com/jsp/jstl/core"; %> <%@ > > taglib prefix="sql" uri="http://java.sun.com/jsp/jstl/sql"; %> <%@ > > taglib prefix="fmt" uri="http://java.sun.com/jsp/jstl/fmt"; %> .. > > <c:choose> > > <c:when test="${empDbInfo.rowCount == 0}"> > > <sql:update> > > INSERT INTO Employee > > (UserName, Password, FirstName, LastName, Dept, > > EmpDate, EmailAddr, ModDate) > > VALUES(?, ?, ?, ?, ?, ?, ?, ?) > > <sql:param value="${param.userName}" /> > > <sql:param value="${param.password}" /> > > <sql:param value="${param.firstName}" /> > > <sql:param value="${param.lastName}" /> > > <sql:param value="${param.dept}" /> > > <sql:dateParam value="${parsedEmpDate}" type="date" /> > > <sql:param value="${param.emailAddr}" /> > > <sql:dateParam value="${now}" /> > > </sql:update> > > </c:when> > > <c:otherwise> > > <sql:update> > > UPDATE Employee > > SET Password = ?, > > FirstName = ?, > > LastName = ?, > > Dept = ?, > > EmpDate = ?, > > EmailAddr = ?, > > ModDate = ? > > WHERE UserName = ? > > <sql:param value="${param.password}" /> > > <sql:param value="${param.firstName}" /> > > <sql:param value="${param.lastName}" /> > > <sql:param value="${param.dept}" /> > > <sql:dateParam value="${parsedEmpDate}" type="date" /> > > <sql:param value="${param.emailAddr}" /> > > <sql:dateParam value="${now}" /> > > <sql:param value="${param.userName}" /> > > </sql:update> > > </c:otherwise> > > </c:choose> > > > > -- > Rick > > --------------------------------------------------------------------- > 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] > > --------------------------------------------------------------------- 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]
