Greetings,
The website I'm supporting is running both TOMCAT applications('.war'),
and has mod_perl scripts (all of them are registry - CGIscripts).
I have the following requirements:
The user identification information must be shared between TOMCAT and mod_perl
(so that the user does not need
What you could do is write an Apache::Session driver that instead of
storing to a file, passes the session id as a call to a web service that
gets and sets session data using parameters sent to a servlet running in
the same context as the sessions where your Java servlets/JSPs run.
I've not
Greetings,
The website I'm supporting is running both TOMCAT applications ('.war'), and has
mod_perl scripts (all of them are registry - CGI scripts). I have the following
requirements:
* The user identification information must be shared between TOMCAT and mod_perl
(so that the user does
Yair Lenga wrote:
The website I'm supporting is running both TOMCAT applications ('.war'),
and has mod_perl scripts (all of them are registry - CGI scripts). I
have the following requirements:
* The user identification information must be shared between TOMCAT
and mod_perl (so
