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 > 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 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 won't be able to capture specific user data for static entities unless > > you deliver them to end users via some servlet-delivery mechanism. > > > Cheers, > > Simon -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
