or a ServletRequestListener or HttpSessionListener. There are
attribute listeners too. In general,
as convenient as listeners are, they also affect performance.
On Apr 18, 9:51 pm, Nichole nichole.k...@gmail.com wrote:
Or you could use a ServletContextListener or a ServletFilter. They're
Hi,
You should have your own implementation of the class Servlet
Then, you should derive all your own servlets from this child of
Servlet
So, when a call a made to your central server is made, this child of
Servlet will be instantied and you can get which url was called, the
input parameters,
Hi,
Didier's solution will definitely do the job for servlets. Alternatively,
you could use a servlet filter to wrap all calls to specific URL mappings
that allows you to capture the same data, without the need for a common base
class, as well as capturing data for dynamic pages as well.
You
Or you could use a ServletContextListener or a ServletFilter. They're
components so easy to swap in an out of your
architecture.
On Apr 18, 4:04 am, Simon Knott knott.si...@gmail.com wrote:
Hi,
Didier's solution will definitely do the job for servlets. Alternatively,
you could use a servlet
