Advertisement :
   Log In    OR    Register  
  Topics :  
RMI Example

Home >>> Hibernate Tutorial >>> Interceptor use log SQL statements >>> example code
Struts Tutorials:
Struts2 Tag CheckBoxList
, Checkbox, Iterator, IF
Struts2 Tag Library Example Struts2 Tiles Example Struts2 Tiles I18N Example Struts2 Questions Struts Tiles I18N Example Struts Eclipse MVC Struts2 Tags Struts2 Example and Tutorial Struts MVC Struts2 Validation
Hibernate Tutorials: Hibernate Case Study Class Hierarchy Persist Example Using Hibernate Interceptor Hibernate Questions with Answer Hibernate Many-to-Many Mapping Example Hibernate one-to-many Mapping Example Hibernate and ORM tools Spring Hibernate Example Hibernate SessionFactory Example Hibernate Mapping Class Hierarchy Hibernate Questions Hibernate SessionFactory Questions Spring Hibernate Example: Spring Hibernate Case Study

Written By : Amit
Title :
Interview Questions
Description : On Hibernate
More...


Written By : Amit
Title :
mapping class hierarchy table per subclass
Description : Example
More...


Written By : Amit
Title :
ways create Hibernate SessionFactory
Description : Example
More...


Written By : Amit
Title :
Spring Hibernate Integration example
Description : Example
More...


Written By : Amit
Title :
ORM Hibernate Best FIT
Description : Discussion
More...


Written By : Amit
Title :
One to Many mapping example
Description : Code
More...

Tags/Keywords : example-code - Interceptor-use-log-SQL-statements - Hibernate-Tutorial Example
Author : Amit
Date (Year/Month/Date): 2009-02-18 Using Hibernate interceptors to log SQL statements

Please be informed that NONE of the design/code from this
page is claiming to be some sort of best practices and we DO NOT expect
any of our visitor/reader of this page to assume this as some sort of
best practice for any context and should not be using this 
as it is without appropriate evaluation to their, so to say, 
specific programming context.

This page intends only to provide bit and piece of known ways  for
doing some sort of example and may not be fit for any other purpose.

Interceptors can be used in cases where we may require
some sort of callback methods called just before the
actual operation is called. For example If it is required
to log any perticular SQL in some different log/audit file,
then we can set a simple Interceptor like CaptureSQL or
LogSQL, just while opening Sesson using SessionFactory
openSession (Interceptor) method.

Following sample interceptor does the logging of SQL
on prepare statement.

Advertisement :
import org.apache.log4j.Logger;
import org.hibernate.EmptyInterceptor;

public class CaptureSQL extends EmptyInterceptor {
    private static Logger log = Logger.getLogger("L1");
	public String onPrepareStatement(String sql) {
		log.debug("Loging SQL statement ...... start");
		log.debug(sql);
		log.debug("Loging SQL statement ...... end");
		return sql;
	}
}
CaptureSQL is the user defined class that extends org.hibernate.EmptyInterceptor to become receiving callback overridden method, such as "onPrepareStatement", when ever a Session is opened, by calling SessionFactory.openSession(new CaptureSQL()). Appropriate log4j.properties file should be configured to be able to handle these logging part. My sample log4j.properties file is as follows:
log4j.rootLogger=DEBUG
log4j.logger.L1=INHERIT, L
log4j.appender.L=org.apache.log4j.FileAppender
log4j.appender.L.file=sample.txt
log4j.appender.L.layout=org.apache.log4j.PatternLayout
log4j.appender.L.layout.ConversionPattern=%d [%t] %C{1} - %m%n
And the Client code is as follows:
log4j.rootLogger=DEBUG
log4j.logger.L1=INHERIT, L
log4j.appender.L=org.apache.log4j.FileAppender
log4j.appender.L.file=sample.txt
log4j.appender.L.layout=org.apache.log4j.PatternLayout
log4j.appender.L.layout.ConversionPattern=%d [%t] %C{1} - %m%n
On executing Client code we can see logs are getting written onto the sample.txt log file, as shown follows: 2009-01-04 09:01:11,578 [main] CaptureSQL - Loging SQL statement .start 2009-01-04 09:01:11,593 [main] CaptureSQL - <<Your SQL used for the operation on the Session opened with CatureSQL as interceptor>> 2009-01-04 09:01:11,593 [main] CaptureSQL - Loging SQL statement .end There are many other interesting callback methods can be used from EmptyInterceptor, such as findDirty -> to check where the Entity in use is dirty or not. -> if this method returns an empty int[] array, then the Entity object supplied in argument of this method is not dirty. -> if this method returns an empty int[] array, then the Entity object is dirty or is updated by some other process in database. -> by returning a null from the overridden findDirty method one can opt for using Hibernate's own or default dirty checking mechanism. onLoad -> it is called just before Entity object is initialized. onDelete -> it is called just before Entity object is deleted. and many more callback methods as defined in org.hibernate.Intercept interface. Hibernate Question on Interceptor 2: Can there be any Interceptor for SessionFactory, so that it can be used across all the Session from this SessionFactory? Yes, there can be an Interceptor defined in org.hibernate.cfg.Configuration to be defined during SessionFactory creation. Configuration.setInterceptor method can be used for this purpose. Hibernate Question on Interceptor 3: Can one be able to use Hibernate Session from within the callback methods of Interceptor? No, Session may not be used from the callback methods of Interceptor. Hibernate Question on Interceptor 4: Can the collection be recreated/initialized lazily while executing any callback method from Interceptor?
Advertisement :
No, Collection may not be lazily initialized, from callback method of Interceptors.
Author of this article/writeup has expressed his/her willingness
to help or guide users with any technical difficulties he/she faces while working with the example code environment setting up, running and resolving any such exception raised during compile or at runtime. You may ask for any technical doubt or seek technical help related to this article by using following form to reach for technical help from the Author for FREE. This article's Author shall be reading your request and responding within reasonable time (no resolution timeframe defined as such).


	
Are you interested in solving a very interesting Technology Stack while Playing this Game          

Please write your Comment on this Matter
(This will be visible if found suitable):
Name: *
Email (will not be displayed): *
Matter: *
17,28
Enter bigger number from above :*
Home >>> Hibernate Tutorial >>> Interceptor use log SQL statements >>> example code
Visitor/User referred related external URL:
(Visible upon review and approved by this site Administrator)
Referred By Name *:
Resource URL *: (e.g, URL should be starting with http://www.-----.---)
 
Resource Short Description *:
5,19
Enter bigger number from above : *

Please log in to add or reply to any matter<- requires login
Log in or Register
Copyright © 2008-2009, Interview-Questions-Tips-Forum, All Rights Reserved.
CONTACT    PRIVACY POLICY    DISCLAIMER
Terms of Use and Disclaimer :

This web site provides some of the information about various technologies, example 
code, tips, tutorials etc. Like any printed materials, content of these pages may 
become out of date over a period of time. Therefore all visitor/users of this web 
site are requested/advised to refer to the originating parties/sources for the 
latest changes and happenings for detailed information. This information is not 
intended to be a substitute for the original reference provided by the originating 
parties/sources.

By accessing and using this website in any ways, including, without
limitation, browsing the website pages, using any information, using any content and/or 
downloading any materials, you agree to and are bound by the terms of use 
described in this page and Usage Terms and Conditions. 
If you do not agree to all of 
the terms and conditions contained in the terms of use described in this
page and Usage Terms and Conditions, do not use this 
website in any manner. If you are using the website on behalf of your 
employer, you represent that you are authorized to accept these Terms of Use 
on your employer's behalf.

All Trademarks are property of their respective owner. Appropriate measure is being
taken for providing accurate and up-to-date information but like any printed materials,
these blog(s)/contents may eventually be outdated one day, so if you are using any 
of these information, please refer original content/documentation from respective sources. 
And under no circumstances shall the Author of these contents and/or this web site
be liable for any loss, damage, expense incurred or suffered which is claimed to have
occurred because of usage of the contents of this web site.
If you have any questions/queries/feedback/suggestions then please write to this web
site owner at contact.