Click here to download eclipse supported ZIP file
Hibernate update should be used where we know that we are only updating the entity information. This operation adds the entity object to persistent context and further changes are tracked and saved when transaction is committed. Let’s check this behavior with a simple program.
EmployeeBean eb = (EmployeeBean) sess.load( EmployeeBean.class, new Long(69) ); eb.setName("PK"); sess.flush(); // changes to eb are automatically detected and persisted
Here is the example code to test update functionality :
This is hibernate.cfg.xml file for connecting the postgreSQL database.
|
This is EmployeeBean.hbm.xml mapping file for map the Entity(POJO) class to columns.
|
This is EmployeeBean.java Entity(POJO) class having the fields needs to be configured in mapping file.
|
This is Update.java main class having the application business logic.
|
This is HibernateUtil.java utility class for getting the database connection.
|
This is log4j.properties file having the entries for logging the information into the console/file.
#By default enabling Console appender # Root logger option log4j.rootLogger=INFO, stdout # Redirect log messages to console log4j.appender.stdout=org.apache.log4j.ConsoleAppender log4j.appender.stdout.Target=System.out log4j.appender.stdout.layout=org.apache.log4j.PatternLayout log4j.appender.stdout.layout.ConversionPattern=%-5p [%c]:%L -->> %m%n # Redirect log messages to a log file #log4j.appender.file=org.apache.log4j.RollingFileAppender #log4j.appender.file.File=C:\\servlet-application.log #log4j.appender.file.MaxFileSize=5MB #log4j.appender.file.MaxBackupIndex=10 #log4j.appender.file.layout=org.apache.log4j.PatternLayout #log4j.appender.file.layout.ConversionPattern=%d{yyyy-MM-dd HH:mm:ss} %-5p %c{1}:%L - %m%n |
This is pom.xml file having the entries of dependency jars and information to build the application .
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" |
No comments:
Post a Comment