I am using ATG9.1. In jsp page I am unable to get prelude.jspf. In ATG10 we it (<include-prelude>/common/prelude.jspf</include-prelude>) is working fine. I want to try for ATG9.1. Can someone make it clear?
I am using ATG 9.1, mysql 5.1, jboss4.2..
I am using /common/prelude.jsp:
I have src/a.b.c.ResourceBundle.properties,
While I am running application, getting below error:
18:48:14,342 ERROR [ContainerBase] Servlet.service() for servlet jsp threw exception
org.apache.jasper.JasperException: /addClub.jsp(43,10) According to TLD or attribute directive in tag file, attribute bundle does not accept any expressions
18:48:13,625 ERROR [ContainerBase] Servlet.service() for servlet jsp threw exception
The issue seems to be related to version mismatch of JSTL. Your web-app deployment descriptor (web.xml) is declared for spec version 2.4 so you should be using JSTL 1.1 which is compatible for 2.4. The URI which you specified is
<%@ taglib prefix="fmt" uri="http://java.sun.com/jstl/fmt" %> which is valid for JSTL 1.0 and you should be using correct URI for JSTL 1.1 as below:
For core: <%@ taglib prefix="c" uri="http://java.sun.com/jsp/jstl/core" %>
For fmt: <%@ taglib prefix="fmt" uri="http://java.sun.com/jsp/jstl/fmt" %>
If I'm clicking /WEB-INF/tld/fmt.tld tld, I am able to show URI=http://java.sun.com/jstl/fmt and /WEB-INF/tld/fmt.tld, URI=http://java.sun.com/jstl/core.
So can you tell what should I do to correct it?
You are seeing that in tld because that tld itself might be for JSTL1.0
Referring taglibs through web.xml is no longer required since JSP 2.0 which is what you would be using when you specify "2.4" in web.xml. So you can comment out all the taglib references from your web.xml. Refer to taglibs through compatible URI from JSPs only. You can create a top.jspf or taglibs.jsp which can have all the taglib references as below:
You can then include this page in other pages at the top manually or through prelude.
Also check the jstl.jar and standard.jar present within WEB-INF\lib. Open the manifest file for both these JARs and check the Specification-Version specified there which should also match the version you are trying to use (1.1 in this case).