Hello Toni,<br><br>that's exactly what I want!<br><br>Thank you for your great support (and the patience ;-)<br><br>Best regards,<br>Fabian<br><br><div><span class="gmail_quote">2006/8/13, Toni Pérez <<a href="mailto:tp.ocms@gmail.com">
tp.ocms@gmail.com</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">On 13/08/06, Fabian Huber <<a href="mailto:fabian.huber@gmail.com">
fabian.huber@gmail.com</a>> wrote:<br>> Hello Toni,<br>><br>> * Yes, I reverted all my changes in the web.xml file.<br>><br>> * The start tag in the web.xml file is:<br>> <web-app xmlns="<a href="http://java.sun.com/xml/ns/j2ee">
http://java.sun.com/xml/ns/j2ee</a>" xmlns:xsi="<br>> <a href="http://www.w3.org/2001/XMLSchema-instance">http://www.w3.org/2001/XMLSchema-instance</a>" xsi:schemaLocation="<br>> <a href="http://java.sun.com/xml/ns/j2ee">
http://java.sun.com/xml/ns/j2ee</a><br>> <a href="http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd</a>" version="2.4"><br>><br>> * The jsp where the problem exists, doesn't use any taglib. The problem is,
<br>> when I try to use OpenCms Macro Expressions. Here is an example:<br>><br>> <%@ page session="false" %><br>> <%@ taglib prefix="cms" uri="<a href="http://www.opencms.org/taglib/cms">
http://www.opencms.org/taglib/cms</a>" %><br>> <jsp:useBean id="cms" class="org.opencms.jsp.CmsJspActionElement"><br>><br>> <link rel="stylesheet" type="text/css"
<br>> href="sites/default/kljb/css/articlemodule.css"><br>><br>> <%<br>> cms.init(pageContext, request, response);<br>><br>> // get the template<br>> String template =
cms.property("template", "search");<br>><br>> // The page header<br>> cms.include(template, "head");<br>> // end of template head<br>><br>> String number = "${number}";
<br>><br>> %><br>> <h1> Gallery</h1><br>><br>><br>> <cms:contentload collector="allInFolderDateReleasedDesc"<br>> param="/kljb/gallery/photos/galery_${number}|photoalbum" editable="true">
<br>> <table border="0" width="100%"><br>> <tr><td width="50%"><br>> <h2><cms:contentshow element="Title" /></h2><br>> </td>
<br>> <td><br>> <cms:contentloop element="Thumbs"><br>> <cms:contentshow element="TextBottom" /><br>> </cms:contentloop><br>> </td>
<br>> </tr><br>> <tr><br>> <td><br>> <cms:contentloop element="Thumbs"><br>> <cms:contentshow element="TextTop" /><br>> </cms:contentloop>
<br>> </td><br>> <td><br>> <a href="<cms:link><cms:contentshow element="${opencms.filename}"<br>> /></cms:link>">Ansehen</a><br>> </td>
<br>><br>> </tr><br>> </table><br>><br>> <br/><br/><br>><br>> </cms:contentload><br>><br>><br>><br>><br>> <%<br>><br>> // The page foot
<br>> cms.include(template, "foot");<br>><br>> %><br>><br>> </jsp:useBean><br>><br>><br>> The JSTL Library is parsing this file and takes the parts underlined as<br>> Expression Language. In fact, these parts are OpenCms Macro. Both languages
<br>> have the same syntax. So this is the problem. (I don't know, why the OpenCms<br>> developers decided to take the syntax of Expression Language for Macro<br>> Expression, too. Ist there any sense?)<br>><br>
> You are working with macros in your jsp files and don't get this problem?<br>><br>> Regards,<br>> Fabian<br><br><br>Hello, Fabian!<br><br>Short answer:<br>In that JSP you could insert the following statement at the beginning:
<br><%@ page isELIgnored="true" %><br>You could see this page to read a little explanation:<br><a href="http://java.sun.com/products/jsp/syntax/2.0/syntaxref2010.html#15653">http://java.sun.com/products/jsp/syntax/2.0/syntaxref2010.html#15653
</a><br><br><br>Not so short answer:<br>You could read the "A.1.1.How JSTL 1.1 Backwards Compatibility is<br>Achieved" point of the JSTL 1.1 specification downloable from here:<br><a href="http://jcp.org/aboutJava/communityprocess/final/jsr052/index2.html">
http://jcp.org/aboutJava/communityprocess/final/jsr052/index2.html</a><br><br>I paste the most important sentences (in my opinion) of that point:<br>"The key difference between JSTL 1.0 and JSTL 1.1 is that the<br>expression language
<br>(EL) has moved from the JSTL specification to the JSP specification. The EL is<br>therefore now part of the JSP 2.0 specification, and JSTL 1.1 requires JSP 2.0<br>(J2EE 1.4 platform).<br><br>A web application developed for JSP
1.2 has a servlet 2.3 deployment descriptor<br>(web.xml). JSP 2.0 provides backwards compatibility for JSP 1.2 web<br>applications by<br>disabling by default the EL machinery (i.e. evaluation of EL expressions) when a<br>
web application has a servlet 2.3 deployment descriptor. A web application that<br>uses JSTL 1.0 and which is deployed with a servlet 2.3 deployment descriptor<br>therefore runs without any modification in a J2EE 1.4 environment because EL
<br>expressions are ignored by JSP 2.0, and JSTL 1.0 keeps evaluating them as was<br>the case with JSP 1.2."<br><br>I hope this helps this time. ;-)<br>Regards.<br> Toni.<br><br>P.S.: I also don't know why Alkacon use a syntax similar to the EL in
<br>their Macro Expressions.<br><br>_______________________________________________<br>This mail is sent to you from the opencms-dev mailing list<br>To change your list options, or to unsubscribe from the list, please visit
<br><a href="http://lists.opencms.org/mailman/listinfo/opencms-dev">http://lists.opencms.org/mailman/listinfo/opencms-dev</a><br></blockquote></div><br>