Page History

...

Start every JSP that should in any way be able to cache with the JSP directive:
Code Block
theme Eclipse
<%@ page language="java" session="false" buffer="none" %>
Include only those tag libraries that are necessary.
Avoid as much as possible non-XML compliant JSPs, such as:
Code Block
theme Eclipse
<a href="<c:out value="${link.url}"/>">title</a>
GX uses JSP Version 2.0 which contains an improved version of the Expression Language (EL), and allows the above to be written as follows:
Code Block
theme Eclipse
<a href="${link.url}">title</a>
The content of JSPs has to conform to the following JSP code conventions

http://java.sun.com/developer/technicalArticles/javaserverpages/code_conventio
http://www.oracle.com/technetwork/java/codeconvtoc-136057.html

Note

title	Don'ts

JSPs are designed to contain HTML and scripting code, not Java code. In combination with the special <% %> tag (the so-called scriptlets), it is possible to include Java code in the JSP. Try to avoid using these scriptlets because this conflicts with the separation of content, business logic and the design template and it may conflict with the caching mechanism.
Don’t use the <jsp:include> tag to include a JSP. Instead use the XperienCentral alternative: <wm:includeUrl url=""/>.
Don’t mix XperienCentral sessions with common Java sessions.

...

XML Descriptor File

...