Spring & JPA with Hibernate and EclipseLink

This is to show how to setup JPA with Spring, using Hibernate and EclipseLink respectively. We are not talking about ORM, which is a separate topic. So I am going to use a simple POJO.

 

First, let's create a simple class:

package my.test;

public class Book
{
    public int bookId;
    public String bookName;
    public String category;
}

Here I don't have getter/setter, since I will have field access later. But in the real world, you may have to use getter/setter if there is any lazy loading.

 

Then we create a DAO interface:

package my.test;

public interface BookDao
{
    void save(Book book);

    Book update(Book book);

    void delete(Book book);

    Book findById(int bookId);
}

Next, we are going to create a JPA entity-mapping file. Alternatively, we could use annotations in Book class. but I don't like this approach since in my environment, the domain models are relatively very large in size. I don't want "pollution" of any underlying implementations. So here is the entity mapping:

<?xml version="1.0" encoding="UTF-8" ?>

<entity-mappings xmlns="http://java.sun.com/xml/ns/persistence/orm"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://java.sun.com/xml/ns/persistence/orm
                        http://java.sun.com/xml/ns/persistence/orm_2_0.xsd"
    version="2.0">

    <entity class="my.test.Book" access="FIELD">
        <table name="mytest_book"/>
        <attributes>
            <id name="bookId"><column name="book_id"/></id>
            <basic name="bookName"><column name="book_name"/></basic>
            <basic name="category"><column name="category"/></basic>
        </attributes>
    </entity>
</entity-mappings>

I saved this file as book.jpa.xml under package my.test.dao.jpa. Note in JPA, usually we use an orm.xml for entity mapping under META-INF directory. But spring saves me a headache, I can put them anywhere I want. For more info, check: http://wiki.eclipse.org/EclipseLink/Examples/JPA/EclipseLink-ORM.XML

 

Now let's create the DAO implementation, using spring. 

package my.test.dao.jpa;

import my.test.Book;
import my.test.BookDao;

import javax.persistence.EntityManager;
import javax.persistence.PersistenceContext;

public class BookDaoJpaImpl implements BookDao
{
    @PersistenceContext
    private EntityManager em;

    public void save(Book book)
    {
        this.em.persist(book);
    }

    public Book update(Book book)
    {
        return this.em.merge(book);
    }

    public void delete(Book book)
    {
        this.em.remove(book);
    }

    public Book findById(int bookId)
    {
        return this.em.find(Book.class, bookId);
    }
}

Note that EntityManager is in general not thread safe, but this instance injected by Spring is thread safe since it will create a new transactional entity manager for each thread. Another note is that the annotation usage here is within the DAO implementation, it's not "polluting" my domain model.

 

Now we need to create the standard persistence.xml.

<persistence xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="http://java.sun.com/xml/ns/persistence 
                                           http://java.sun.com/xml/ns/persistence/persistence_2_0.xsd"
	version="2.0" xmlns="http://java.sun.com/xml/ns/persistence">

    <persistence-unit name="myPersistenceUnit" transaction-type="RESOURCE_LOCAL">
        <mapping-file>my/test/dao/jpa/book.jpa.xml</mapping-file>
    </persistence-unit>
</persistence>

I saved this file in persistence.xml under package my.dao.jpa. In standard JPA, this file has to be under META-INF in classpath. But Spring saves me another headache. I can put it anywhere I want.

 

Now, we need to create the spring xml to stitch everything together. 

<?xml version="1.0" encoding="UTF-8"?>

<beans xmlns="http://www.springframework.org/schema/beans"
       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       xmlns:context="http://www.springframework.org/schema/context"
       xmlns:aop="http://www.springframework.org/schema/aop"
       xmlns:tx="http://www.springframework.org/schema/tx"
       xmlns:p="http://www.springframework.org/schema/p"
       xsi:schemaLocation="http://www.springframework.org/schema/beans
       http://www.springframework.org/schema/beans/spring-beans-3.0.xsd
       http://www.springframework.org/schema/context
       http://www.springframework.org/schema/context/spring-context-3.0.xsd
       http://www.springframework.org/schema/tx
       http://www.springframework.org/schema/tx/spring-tx-3.0.xsd
       http://www.springframework.org/schema/aop
       http://www.springframework.org/schema/aop/spring-aop-3.0.xsd">

    <bean id="bookDao" class="my.test.dao.jpa.BookDaoJpaImpl"/>

    <!-- bean post-processor for JPA annotations -->
    <bean class="org.springframework.orm.jpa.support.PersistenceAnnotationBeanPostProcessor"/>

    <aop:config>
        <aop:pointcut id="bookDaoMethods" expression="execution(* my.test.dao.jpa.BookDaoJpaImpl.*(..))"/>
        <aop:advisor advice-ref="bookDaoTxAdvice" pointcut-ref="bookDaoMethods"/>
    </aop:config>

    <tx:advice id="bookDaoTxAdvice" transaction-manager="myTxManager">
        <tx:attributes>
            <tx:method name="*" propagation="REQUIRED"/>
        </tx:attributes>
    </tx:advice>

    <bean id="myTxManager" class="org.springframework.orm.jpa.JpaTransactionManager">
        <property name="entityManagerFactory" ref="myEmf"/>
    </bean>   

    <bean id="mydataSource" class="org.apache.commons.dbcp.BasicDataSource" destroy-method="close">
        <property name="driverClassName" value="${jdbc.driver}"/>
        <property name="url" value="${jdbc.url}"/>
        <property name="username" value="${jdbc.username}"/>
        <property name="password" value="${jdbc.password}"/>
        <property name="maxIdle" value="10"/>
        <property name="maxActive" value="100"/>
        <property name="maxWait" value="10000"/>
        <property name="testOnBorrow" value="true"/>
        <property name="testWhileIdle" value="true"/>
        <property name="timeBetweenEvictionRunsMillis" value="1200000"/>
        <property name="minEvictableIdleTimeMillis" value="1800000"/>
        <property name="numTestsPerEvictionRun" value="5"/>
        <property name="defaultAutoCommit" value="true"/>
    </bean>

    <context:property-placeholder location="classpath:my/test/dao/jpa/jdbc.properties"/>
</beans>

Here we define the DAO class, the transaction manager, and the datasource. The jdbc.properties is like this:

jdbc.driver=oracle.jdbc.OracleDriver
jdbc.url=jdbc:oracle:thin:@*****
jdbc.username=
jdbc.password=

So far we haven't define the EntityManagerFactory yet, since we still stays in JPA.

 

If we use Hibernate as the JPA implementation, the EntityManagerFactory is like this:

<bean id="myEmf" class="org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean">
        <property name="persistenceUnitName" value="myPersistenceUnit"/>
        <property name="dataSource" ref="mydataSource"/>
        <property name="persistenceXmlLocation" value="classpath:my/test/dao/jpa/persistence.xml"/>
        <property name="loadTimeWeaver">
            <bean class="org.springframework.instrument.classloading.InstrumentationLoadTimeWeaver"/>
        </property>
        <property name="jpaVendorAdapter">
            <bean class="org.springframework.orm.jpa.vendor.HibernateJpaVendorAdapter">
                <!-- <property name="showSql" value="true"/> -->
                <property name="generateDdl" value="false"/>
                <property name="database" value="ORACLE"/>
                <property name="databasePlatform" value="org.hibernate.dialect.OracleDialect"/>
            </bean>
        </property>
    </bean>

The only thing specific to Hibernate is the jpaVendorAdapter entry. Also note here we specify the persistence.xml location. For more info on load time weaver, check: http://static.springsource.org/spring/docs/2.5.6/reference/orm.html#orm-jpa-setup-lcemfb and 

http://www.eclipse.org/aspectj/doc/released/devguide/ltw.html

 

If we use EclipseLink, then the above bean becomes:

<bean id="myEmf" class="org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean">
        <property name="persistenceUnitName" value="myPersistenceUnit"/>
        <property name="dataSource" ref="mydataSource"/>
        <property name="persistenceXmlLocation" value="classpath:my/test/dao/jpa/persistence.xml"/>
        <property name="loadTimeWeaver">        
            <bean class="org.springframework.instrument.classloading.InstrumentationLoadTimeWeaver"/>
        </property>
        <property name="jpaVendorAdapter">
            <bean class="org.springframework.orm.jpa.vendor.EclipseLinkJpaVendorAdapter">
                <property name="generateDdl" value="false"/>
                <property name="database" value="ORACLE"/>
                <property name="databasePlatform" value="org.eclipse.persistence.platform.database.OraclePlatform"/>
            </bean>
        </property>
</bean>

For spring: we need to following jars: spring jars and commons-logging. We also need aspectjweaver.jar and aopalliance.jar

 

For hibernate: we need hibernate jar,  the jars in the required directory, and the jar in the jpa directory.

 

For eclipselink: we need eclipselink jar and standard persistence 2.0 jar.

 

and don't forget jdbc driver jar, I am just using oracle. I am also using commons dbcp and pool jars.

 

If you are using eclipselink, don't forget to use -javaagent: <spring instrument jar>. Hiberate doesn't need this switch.

 

And for jdbc/orm, don't forget the nice handy small tool: p6spy. It could print out full SQL statements without ? marks.

 

Here are some references:

Hibernate: http://www.hibernate.org/

EclipseLink: http://www.eclipse.org/eclipselink/

JPA: http://jcp.org/en/jsr/detail?id=317

P6spy: http://sourceforge.net/projects/p6spy/

SQLProfiler: http://sourceforge.net/projects/sqlprofiler/

 

基于遗传算法的新的异构分布式系统任务调度算法研究(Matlab代码实现)内容概要:本文档围绕基于遗传算法的异构分布式系统任务调度算法展开研究,重点介绍了一种结合遗传算法的新颖优化方法,并通过Matlab代码实现验证其在复杂调度问题中的有效性。文中还涵盖了多种智能优化算法在生产调度、经济调度、车间调度、无人机路径规划、微电网优化等领域的应用案例,展示了从理论建模到仿真实现的完整流程。此外,文档系统梳理了智能优化、机器学习、路径规划、电力系统管理等多个科研方向的技术体系与实际应用场景,强调&ldquo;借力&rdquo;工具与创新思维在科研中的重要性。; 适合人群:具备一定Matlab编程基础,从事智能优化、自动化、电力系统、控制工程等相关领域研究的研究生及科研人员,尤其适合正在开展调度优化、路径规划或算法改进类课题的研究者; 使用场景及目标:①学习遗传算法及其他智能优化算法(如粒子群、蜣螂优化、NSGA等)在任务调度中的设计与实现;②掌握Matlab/Simulink在科研仿真中的综合应用;③获取多领域(如微电网、无人机、车间调度)的算法复现与创新思路; 阅读建议:建议按目录顺序系统浏览,重点关注算法原理与代码实现的对应关系,结合提供的网盘资源下载完整代码进行调试与复现,同时注重从已有案例中提炼可迁移的科研方法与创新路径。
【微电网】【创新点】基于非支配排序的蜣螂优化算法NSDBO求解微电网多目标优化调度研究(Matlab代码实现)内容概要:本文提出了一种基于非支配排序的蜣螂优化算法(NSDBO),用于求解微电网多目标优化调度问题。该方法结合非支配排序机制,提升了传统蜣螂优化算法在处理多目标问题时的收敛性和分布性,有效解决了微电网调度中经济成本、碳排放、能源利用率等多个相互冲突目标的优化难题。研究构建了包含风、光、储能等多种分布式能源的微电网模型,并通过Matlab代码实现算法仿真,验证了NSDBO在寻找帕累托最优解集方面的优越性能,相较于其他多目标优化算法表现出更强的搜索能力和稳定性。; 适合人群:具备一定电力系统或优化算法基础,从事新能源、微电网、智能优化等相关领域研究的研究生、科研人员及工程技术人员。; 使用场景及目标:①应用于微电网能量管理系统的多目标优化调度设计;②作为新型智能优化算法的研究与改进基础,用于解决复杂的多目标工程优化问题;③帮助理解非支配排序机制在进化算法中的集成方法及其在实际系统中的仿真实现。; 阅读建议:建议读者结合Matlab代码深入理解算法实现细节,重点关注非支配排序、拥挤度计算和蜣螂行为模拟的结合方式,并可通过替换目标函数或系统参数进行扩展实验,以掌握算法的适应性与调参技巧。
本项目是一个以经典51系列单片机&mdash;&mdash;STC89C52为核心,设计实现的一款高性价比数字频率计。它集成了信号输入处理、频率测量及直观显示的功能,专为电子爱好者、学生及工程师设计,旨在提供一种简单高效的频率测量解决方案。 系统组成 核心控制器:STC89C52单片机,负责整体的运算和控制。 信号输入:兼容多种波形(如正弦波、三角波、方波)的输入接口。 整形电路:采用74HC14施密特触发器,确保输入信号的稳定性和精确性。 分频电路:利用74HC390双十进制计数器/分频器,帮助进行频率的准确测量。 显示模块:LCD1602液晶显示屏,清晰展示当前测量的频率值(单位:Hz)。 电源:支持标准电源输入,保证系统的稳定运行。 功能特点 宽频率测量范围:1Hz至12MHz,覆盖了从低频到高频的广泛需求。 高灵敏度:能够识别并测量幅度小至1Vpp的信号,适合各类微弱信号的频率测试。 直观显示:通过LCD1602液晶屏实时显示频率值,最多显示8位数字,便于读取。 扩展性设计:基础版本提供了丰富的可能性,用户可根据需要添加更多功能,如数据记录、报警提示等。 资源包含 原理图:详细的电路连接示意图,帮助快速理解系统架构。 PCB设计文件:用于制作电路板。 单片机程序源码:用C语言编写,适用于Keil等开发环境。 使用说明:指导如何搭建系统,以及基本的操作方法。 设计报告:分析设计思路,性能评估和技术细节。
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值