Hi
Bertrand LEGA wrote:
I would be glad to hear your thoughts about using the jcr session in a J2EE web application.
Basically, there are two solutions :
1. create a session to the jcr each time a page access to the repository. It is basically what's the jcr tags propose to do :
The session is destroyed when the processing of the jsp page is done. 2. Create a jcr session when the HttpSession is created and use it during the user session (ie the jcr session stored in the httpsession). This jcr session is destroyed when the HttpSession will be (using a HttpSessionListener for example).
Both approaches are supported in the jcr taglib.
the example 2 would be
in a SessionListener:
session.setAttribute("mySessionKey",mySession)in jsp:
<jcr:nodes node="/" var="node" traverserDepth="1" session="mySessionKey">
<c:out value="${node.path}"/>
</jcr:nodes>
Personnally, I would prefer the solution 2.
me too
What do you think about it ?
Do you know if tests had been carried with a important number of concurrent sessions (100-1000) ?
Regards, Bertrand.
regards edgar
This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
