mfs wrote:
Given the above context, i was wondering if there is some way i can provide
my own unique sessionId to the servlet container whenever it creates a
unique http session against a user.
You would need to write your own manager. You should be able to extend
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Farhan,
mfs wrote:
| Actually we have our own session tracking framework, and now
| that i am making a seperate servlet based application, i have come to need
| to support interoperability between Servlet HttpSession and the sessions
| maintained by
so thats not something exposed by the servlet api itself...if i understand u
correctly?, well though for my development i use tomcat/jetty servlet
containers, but our app is deployed on the oracle app server, which has its
own mini servlet engine (OSE), now given that i would need to extend the
Actually they don't, its a non-java based framework.
But Christoper i would still be interested in knowing the approach you took,
sounds like an interesting deal to me, now when u say wrap the servlet's
container's framework, what extended functionality did you provide in that
case in your
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Farhan,
mfs wrote:
| Actually they don't, its a non-java based framework.
:(
| But Christoper i would still be interested in knowing the approach you
took,
| sounds like an interesting deal to me, now when u say wrap the servlet's
| container's
Guys,
Might not be the question for this list, but still to thought to check.
Is there a way i can provide the unique sessionID to the servlet
api/container, instead of it generating its own (whenever a new HttpSession
is created). Actually we have our own session tracking framework, and now
