tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Craig R. McClanahan" <craig...@apache.org>
Subject Re: Webapp - WebappServer interaction
Date Thu, 01 Aug 2002 15:39:15 GMT


On Thu, 1 Aug 2002, SB wrote:

> Date: Thu, 1 Aug 2002 07:14:08 -0400
> From: SB <step1b@cyberspace.org>
> Reply-To: Tomcat Users List <tomcat-user@jakarta.apache.org>
> To: tomcat-user@jakarta.apache.org
> Subject: Webapp - WebappServer interaction
>
> Just curious,
> Can a webapp know what appserver it is running on?
>

See ServletContext.getServerInfo().

> The very purpose of an appserver is to keep the webapp
> free from the mundane housekeeping stuff like
> session management and secure access. The webapp
> is completely unaware of these issues. Instead,
> is it possible for a webapp to provide its own
> or possibly override appserver's session management
> - or say inherit these from the app server thus
> extending it?
>

That's totally dependent on the appserver's architecture and organization.

Tomcat has mechanisms to plug replacements for things like valves, realms,
and so on -- including, as it happens, the session manager.  You wwould
need to become very familiar with the internal architecture (you can
download the sources from the Jakarta web site), and in particular
understand how all of the class loaders work, before you'll be very
successful.

At least for Tomcat, and most likely for any other container, a webapp
cannot do this kind of thing at runtime -- it takes modifications to
server.xml to pull this off.

> --st
>

Craig


--
To unsubscribe, e-mail:   <mailto:tomcat-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-user-help@jakarta.apache.org>


Mime
View raw message