Hi Richard,
[EMAIL PROTECTED] wrote:
Thanks for the ideas. I was hoping not to bind the AuditInterceptor too
tightly to the Servlet API. To do that I might have to pass in the username
and IP address as separate parms, and of course have to set these up in
advance. But I can also just have a di
Rob,
Thanks for the ideas. I was hoping not to bind the AuditInterceptor too
tightly to the Servlet API. To do that I might have to pass in the username
and IP address as separate parms, and of course have to set these up in
advance. But I can also just have a different implementation for
non-se
Hi,
[EMAIL PROTECTED] wrote:
Question
Is there a bean I can wire into
src/main/resources/applicationContext-dao.xml that provide access to the
following properties for a request: logged-in username, IP address the
request originated from ??
I am thinking the ACEGI framework (or an appfuse class
Question
Is there a bean I can wire into
src/main/resources/applicationContext-dao.xml that provide access to the
following properties for a request: logged-in username, IP address the
request originated from ??
I am thinking the ACEGI framework (or an appfuse class that implements and
ACEGI inte
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Take a look at:
http://www.codeczar.com/projects/components/logweb/
or just do the same as in
com.yourproject.sample.dao.hibernate.GenericDaoHibernate
and modify eventually log4j configuration in
yourProject/src/main/resources/log4j.xml for configurat