Sometimes when you want to create large portal-like application which consists of a few smaller applications, or you want to create your own SSO domain, you must share session and session data between all interested applications.
Today I will show you how you can share session and data across applications in Apache Tomcat 6.
Enabling session sharing
Open $CATALINA_HOME/conf/server.xml, find the 8080 connector definition:
view sourceprint?1.<Connector port="8080" protocol="HTTP/1.1" connectionTimeout="20000" redirectPort="8443" />and simply add emptySessionPath="true" attribute to it so that it looks something like this:
view sourceprint?1.<Connector port="8080" protocol="HTTP/1.1" emptySessionPath="true" connectionTimeout="20000" redirectPort="8443" />Test projects
I created two simple applications called session1 and session2.
session1 increments the counter:
view sourceprint?01.<%@ taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c"%>
02.<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
03.<html>
04.<head>
05.<title>++</title>
06.</head>
07.<body>
08.<h1>I'm incrementing the counter!</h1>
09.<c:set var="counter" value="${sessionScope.counter + 1}" scope="session" />
10.<h1>Current counter value is ${sessionScope.counter}</h1>
11.</body>
12.</html>session2 decrements the counter:
view sourceprint?01.<%@ taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c"%>
02.<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
03.<html>
04.<head>
05.<title>--</title>
06.</head>
07.<body>
08.<h1>I'm decrementing the counter!</h1>
09.<c:set var="counter" value="${sessionScope.counter - 1}" scope="session" />
10.<h1>Current counter value is ${sessionScope.counter}</h1>
11.</body>
12.</html>Deploying and testing
When I deployed both applications and refreshed a few times their index pages:
view sourceprint?1.http://localhost:8080/session1/
2.http://localhost:8080/session2/although the JSESSIONID cookie was the same:
counters were independent. The first one showed +4, the second one showed -4.
The problem and the solution
Problem: even though the session id is the same in both applications you cannot share data directly using HttpSession object.
Solution: you have to use session-aware cross contexts in order to share data between applications.
Cross contexts in Apache Tomcat
First you have to allow applications to access each others' contexts.
Open $CATALINA_HOME/conf/context.xml and add crossContext="true" attribute to the <Context /> root element:
view sourceprint?1.<?xml version='1.0' encoding='utf-8'?>
2.<Context crossContext="true">
3.<WatchedResource>WEB-INF/web.xml</WatchedResource>
4.<Manager pathname="" />
5.</Context>Re-start the server.
Cross context data sharing
Please note that I highly loath scriptlets, I only show them in order to simplify the listing
Edit index.jsp of the session1 application so that it looks like this:
view sourceprint?01.<%@ taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c"%>
02.<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
03.<html>
04.<head>
05.<title>++</title>
06.</head>
07.<body>
08.<%
09.ServletContext siblingContext = request.getSession().getServletContext().getContext("/session1");
10.Integer counter = (Integer)siblingContext.getAttribute("counter");
11.if (counter == null) {
12.counter = 0;
13.}
14.counter++;
15.request.setAttribute("counter", counter);
16.siblingContext.setAttribute("counter", counter);
17.%>
18.<h1>I'm incrementing counter!</h1>
19.<h1>Current counter value is ${counter}!</h1>
20.</body>
21.</html>Then, modify the session2 application:
view sourceprint?01.<%@ taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c"%>
02.<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
03.<html>
04.<head>
05.<title>--</title>
06.</head>
07.<body>
08.<%
09.ServletContext siblingContext = request.getSession().getServletContext().getContext("/session1");
10.Integer counter = (Integer)siblingContext.getAttribute("counter");
11.if (counter == null) {
12.counter = 0;
13.}
14.counter--;
15.request.setAttribute("counter", counter);
16.siblingContext.setAttribute("counter", counter);
17.%>
18.<h1>I'm decrementing counter!</h1>
19.<h1>Current counter value is ${counter}!</h1>
20.</body>
21.</html>Re-deploy both applications.
Now, when you access both applications, you will see that the counter is now shared.
Session-aware cross context data sharing
Didn't you spot anything weird?
I'm sharing data using ServletContext. Its scope is the application scope, not the session scope.
If you open both pages in different browsers you will see that the counter shares its value.
How to make it session-aware?
Since JSESSIONID is the same, you can create a map and use session id as a key to store session data and then store the map in ServletContext like this:
view sourceprint?1.Map<String, Object> data = new HashMap<String, Object>();
2.String id = request.getSession().getId();
3.data.put(id, counter);
4.siblingContext.setAttribute("data", data);
QQ群⑧：
窥视卡
雷达卡
发表于 2017-1-3 07:09:13
提升卡
置顶卡
沉默卡
喧嚣卡
变色卡
千斤顶
显身卡