How to define a portlet namespace and context paths using JSTL and JSP

Learn how to define portlet namespaces and context paths using JSTL and the JSP expression language.

Living in the portal development world, I'm sure that you're already familiar with the need to namespace unique page elements and the need to use context path to access resources like image, CSS and JS files from within the portlet views. The difficulty is that traditional approaches make the code difficult to read, especially if you followed the archaic method of prefixing your unique entities with the <portlet:namespace/> tag.

I propose an alternative that defines portlet namespaces and portlet context paths using JSTL andJSP> EL.

Author's note: I recently discovered that this so-called archaic method seems to be required by some portal servers (e.g., Liferay 6.2).

Traditional namespace examples

JSP Expression <%=renderResponse.getNamespace()%>
JSTL ${renderResponse.getNamespace()}
Portlet Tag Library <portlet:namespace/>
<form id="<portlet:namespace/>MyFormName$">
<input type="text" id="name$<%=renderResponse.getNamespace()%>" name="name"/>
<input type="Submit" onclick="displayGreeting${renderResponse.getNamespace()}()"/>
</form> <script>
function displayGreeting${renderResponse.getNamespace()} (){
var name =
document.getElementById("name$<%=renderResponse.getNamespace()%>"); alert("Greetings " + name + "!");

Traditional Context Path examples

JSP Expression <%=renderRequest.getContextPath()%>
JSTL ${renderRequest.getContextPath()}
<link rel="stylesheet"

<script src="${renderRequest.getContextPath()}/js/MyProjectJavascript.js"/>

<img src="${renderRequest.getContextPath()}/images/MyProjectImage.png"/>

Proposed solution

I propose defining two JSTL variables to replace the need for unnecessarily cumbersome code. It should clean your code considerably and make it easier to read and debug.

What are the prerequisites?

First and foremost, we need access in our JSPs to the portlet objects. So we absolutely require, at a minimum, the Portlet Tag Libraries and JSTL Tag Library includes, and we mustn't forget to define the portlet objects. So, here's the code:

<%@ taglib prefix="portlet"

<%@ taglib uri="http://java.sun.com/jstl/core_rt" prefix="c"%>

<portlet:defineObjects />

Note: This will be placed at the top of the JSP along with any class and tag library includes, and is already required for the traditional approaches.

How do I define the new portlet namespace and Context Path?

<c:set var="ns" scope="page"

<c:set var="cp" scope="page" 

What does the code look like?

Context Path Example

<link rel="stylesheet"

<script src="${cp}/js/MyProjectJavascript.js"/>

<img src="${cp}/images/MyProjectImage.png"/>

Namespace example

<form id="MyFormName${ns}">
     <input type="text" id="name${ns}" name="name"/>
     <input type="Submit" onclick="displayGreeting${ns}()"/>


     function displayGreeting${ns}(){

           var name =

           alert("Greetings " + name +



What's next?

In my next tip, I'll tackle another common issue: adding portlet namespace support for external JavaScript files and templates.

Dig Deeper on Front-end, back-end and middle-tier frameworks

App Architecture
Software Quality
  • How to test a predictive model

    Strategies for testing predictive models and analytics emphasize data quality, real-time testing and code redundancy, as well as ...

  • The dos and don'ts of visual testing

    The visual aspect of an application is an important part of UX. Defects can potentially result in lost sales and damaged ...

  • 3 QA testing tools to consider

    QA testers need to be able to put applications and APIs through their paces. Here are some examples of tools that can help with ...

Cloud Computing