If it returns null
, then it can only mean 2 things:
- JSF hasn't created the bean beforehand yet.
- The applet-servlet interaction doesn't use the same HTTP session as the webapp.
Given the way how you described the functional requirement, I think it's the latter. You need to ensure that you pass the session identifier of the webapp along with the HTTP request from the applet as well. This can be in the form of the JSESSIONID
cookie or the jsessionid
URL path attribute.
First, you need to tell the applet about the session ID the webapp is using. You can do it by passing a parameter to <applet>
or <object>
tag holding the applet
<param name="sessionId" value="#{session.id}" />
(the #{session}
is an implicit JSF EL variable referring the current HttpSession
which in turn has a getId()
method; you don't need to create a managed bean for that or so, the above line of code is complete as-is)
which can be retrieved in the applet as follows:
String sessionId = getParameter("sessionId");
You didn't describe how you're interacting with the servlet, but assuming that you're using the standard Java SE URLConnection
for this, pointing to the @WebServlet("/servleturl")
servlet, then you can use setRequestProperty()
to set a request header:
URL servlet = new URL(getCodeBase(), "servleturl");
URLConnection connection = servlet.openConnection();
connection.setRequestProperty("Cookie", "JSESSIONID=" + sessionId);
// ...
Alternatively, you can also pass it as a URL path attribute:
URL servlet = new URL(getCodeBase(), "servleturl;jsessionid=" + sessionId);
URLConnection connection = servlet.openConnection();
// ...
(please note that the case matters in the both cases)
Either way, this way the applet-servlet interaction will take place in the same HTTP session as JSF managed beans.
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…