我正在使用JPA和hibernate并尝试连接到数据源来检索信息，但是当我运行应用程序时，我没有得到任何错误但是当我运行以下代码时没有显示结果。问题来自于之前的发布位于here的时候，我正在设置环境，在Glassfish上使用hibernate对JPA进行一些测试。
日志文件显示此
INFO: Not binding factory to JNDI, no JNDI name configured
我的日志文件
INFO: Processing PersistenceUnitInfo [
name: DBAppPU
...]
INFO: Binding entity from annotated class: model.VMatterDetails
INFO: Binding Named query: VMatterDetails.findAll => SELECT v FROM VMatterDetails v
INFO: Binding Named query: VMatterDetails.findByMatterInfoStatus => SELECT v FROM VMatterDetails v WHERE v.matterInfoStatus = :matterInfoStatus
INFO: Binding Named query: VMatterDetails.findByMatterInfoRespLwyr => SELECT v FROM VMatterDetails v WHERE v.matterInfoRespLwyr = :matterInfoRespLwyr
INFO: Binding Named query: VMatterDetails.findByMatterID => SELECT v FROM VMatterDetails v WHERE v.matterID = :matterID
INFO: Binding Named query: VMatterDetails.findByMatterInfoMatterNum => SELECT v FROM VMatterDetails v WHERE v.matterInfoMatterNum = :matterInfoMatterNum
INFO: Bind entity model.VMatterDetails on table vMatterDetails
INFO: Hibernate Validator not found: ignoring
INFO: Instantiated an instance of org.hibernate.validator.engine.resolver.JPATraversableResolver.
INFO: Instantiated an instance of org.hibernate.validator.engine.resolver.JPATraversableResolver.
INFO: Unable to find org.hibernate.search.event.FullTextIndexEventListener on the classpath. Hibernate Search is not enabled.
INFO: Instantiated an instance of org.hibernate.validator.engine.resolver.JPATraversableResolver.
INFO: Initializing connection provider: org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider
INFO: Using provided datasource
INFO: RDBMS: Microsoft SQL Server, version: 10.50.1600
INFO: JDBC driver: jTDS Type 4 JDBC Driver for MS SQL Server and Sybase, version: 1.2.5
INFO: Using dialect: org.hibernate.dialect.SQLServerDialect
INFO: Disabling contextual LOB creation as JDBC driver reported JDBC version [3] less than 4
INFO: Transaction strategy: org.hibernate.ejb.transaction.JoinableCMTTransactionFactory
INFO: instantiating TransactionManagerLookup: org.hibernate.transaction.SunONETransactionManagerLookup
INFO: instantiated TransactionManagerLookup
INFO: Automatic flush during beforeCompletion(): disabled
INFO: Automatic session close at end of transaction: disabled
INFO: Scrollable result sets: enabled
INFO: JDBC3 getGeneratedKeys(): enabled
INFO: Connection release mode: auto
INFO: Default batch fetch size: 1
INFO: Generate SQL with comments: disabled
INFO: Order SQL updates by primary key: disabled
INFO: Order SQL inserts for batching: disabled
INFO: Query translator: org.hibernate.hql.ast.ASTQueryTranslatorFactory
INFO: Using ASTQueryTranslatorFactory
INFO: Query language substitutions: {}
INFO: JPA-QL strict compliance: enabled
INFO: Second-level cache: enabled
INFO: Query cache: disabled
INFO: Cache region factory : org.hibernate.cache.impl.NoCachingRegionFactory
INFO: Optimize cache for minimal puts: disabled
INFO: Structured second-level cache entries: disabled
INFO: Statistics: disabled
INFO: Deleted entity synthetic identifier rollback: disabled
INFO: Default entity-mode: pojo
INFO: Named query checking : enabled
INFO: Check Nullability in Core (should be disabled when Bean Validation is on): disabled
INFO: building session factory
INFO: Not binding factory to JNDI, no JNDI name configured
INFO: Running hbm2ddl schema update
INFO: fetching database metadata
INFO: updating schema
INFO: Instantiated an instance of org.hibernate.validator.engine.resolver.JPATraversableResolver.
INFO: table found: DB12248.dbo.vMatterDetails
INFO: columns: [clientinfostrextra1, matterinfobudgetdisbs, addressinfohomefaxphone, addressinfocompany, addressinfoaddrline2, addressinfoaddrline1, addressinfopager, matterinfodestroydate, matterinfolasttrust, matterinfobilledrcpts, addressinfolastname, matterinfoamtquoted, addressinfoattposition, matterinfolastsoadate, matterinfobilledhours, matterinfoextracasenote2, matterinfoextracasenote1, addressinfoaddrgroup, matterinfobilleddisbs, addressinfowebpage, addressinfohomephone, clientinfoextra2, clientinfoextra1, matterinfostatus, matterinfoextracasenote5, matterinfobilladdid2, matterinfoextracasenote6, matterinfoextracasenote3, matterinfoextracasenote4, addressinfomiddle, addressinfointernetaddr, matterinfoactivematter, clientinfomatterext, matterinfosparelong2, matterinfosparelong1, lawyerid, matterinforeferredbytype, matterid, matterinfobilladdid, matterinfosortname, matterinfodefrateamt, matterinfodefratetype, matterinfodocumentpath, matterinfototfees, matterinfoformatfile, addressinfocarphone, addressinfoextra, matterinfocredithold, matterinfocasenotes, matterinfortnrbal, addressinfohomeemail, matterinfofilelocation, matterinfoextracollectnote4, addressinfocity, matterinfochargeint, matterinfoextracollectnote3, matterinfoextracollectnote6, matterinfoextracollectnote5, addressinfosuffix, matterinfoopendate, matterinfobudgetfees, matterinfoflags, clientinfosortname, clientinfoclientdefault, addressinfofirst, matterinfointerestsettings, matterinfoextracollectnote2, clientinfomatterbase, matterinfoextracollectnote1, addressinfocode, matterinfosoaformat, addressinfocountry, matterinfofiledesc, matterinforeflwyr, matterinfousedefintrate, addressinfoaddrtype, matterinfomatternum, matterinforeferredby, matterinfotypeoflaw, addressinfocellphone, matterinfocollectionnotes, clientinfodocumentpath, matterinfobilledfees, matterinfosparestring, matterinfoarbal, matterinfolastbilled, matterinfolastrcptamount, matterinfototdisbs, addressinfoattlast, matterinfototalhours, matterinfotaxdisbs, matterinfosparedouble, matterinforesplwyr, matterinfolastfeedate, matterinfointrate, addressinfobusphone, addressinfoprov, matterinfocrossreference, addressinfofaxphone, matterinfolastrcptdate, matterinfototrcpts, addressinfotitle, matterinfolastdisbdate]
INFO: foreign keys: []
INFO: indexes: [pk__vmatterd__4d8e0b1a0b5cafea]
INFO: schema update complete
INFO: JNDI InitialContext properties:{}
INFO: Portable JNDI names for EJB VMatterDetailsFacade : [java:global/DBApp/VMatterDetailsFacade, java:global/DBApp/VMatterDetailsFacade!ejb.VMatterDetailsFacadeLocal]
INFO: Instantiated an instance of org.hibernate.validator.engine.resolver.JPATraversableResolver.
INFO: Loading application DBApp at /DBApp
INFO: DBApp was successfully deployed in 3,374 milliseconds.
INFO: Find All Executing
INFO: Find All Return
EJB bean是
@Stateless
public class VMatterDetailsFacade implements VMatterDetailsFacadeLocal {
public static final Logger log = Logger.getLogger("ejb.VMatterDetailsFacade");
@PersistenceUnit(unitName = "DBAppPU")
private EntityManagerFactory emf;
private List<VMatterDetails> matterDetailsList;
protected EntityManager getEntityManager() {
return emf.createEntityManager();
}
@Override
public VMatterDetails find(String str) {
throw new UnsupportedOperationException("Not supported yet.");
}
@Override
public List<VMatterDetails> findAll() {
log.info("Find All Executing");
matterDetailsList = emf.createEntityManager().createNamedQuery("VMatterDetails.findAll").getResultList();
// matterDetails.addAll(em2.createNamedQuery("VMatterDetails.findAll").getResultList());
log.info("Find All Return");
return matterDetailsList;
}
@Override
public int count() {
throw new UnsupportedOperationException("Not supported yet.");
}
我的持久性xml是
<?xml version="1.0" encoding="UTF-8"?>
<persistence version="2.0" xmlns="http://java.sun.com/xml/ns/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">
<persistence-unit name="DBAppPU" transaction-type="JTA">
<provider>org.hibernate.ejb.HibernatePersistence</provider>
<jta-data-source>matterPool12248</jta-data-source>
<properties>
<property name="hibernate.hbm2ddl.auto" value="update"/>
</properties>
</persistence-unit>
</persistence>
答案 0 :(得分：2)
您粘贴的日志未显示任何ERROR（也不是FATAL也不会WARNING）消息，您显示的特定消息只是告诉您没有绑定SessionFactory到JNDI。这没有任何问题，许多应用程序不使用JNDI-bound SessionFactory，这在使用JPA时并不真正相关。所以请忽略这个INFO rmational消息。
实际上，根据日志文件，一切看起来都很好：已检测到您的实体，已处理命名查询，架构已更新（因此与DB的连接正常）等。
话虽这么说，我会先激活SQL日志记录，看看究竟发生了什么（这不会解决问题，但仍然如此）。您可以在persistence.xml中设置以下属性：
<!-- Echo all executed SQL to stdout -->
<property name="hibernate.show_sql" value="true"/>
或者（我更喜欢这个选项，因为我希望能够完全控制日志记录），方法是将日志级别设置为以下类别的调试：
org.hibernate.SQL
并针对数据库运行生成的SQL。
第二件事，我建议使用注入的容器管理EntityManager 而不是使用托管EntityManager的应用程序（这是在托管环境中的首选方式）：
@Stateless
public class VMatterDetailsFacade implements VMatterDetailsFacadeLocal {
public static final Logger log = Logger.getLogger("ejb.VMatterDetailsFacade");
@PersistenceContext(unitName = "DBAppPU")
private EntityManager em;
@Override
public VMatterDetails find(String str) {
throw new UnsupportedOperationException("Not supported yet.");
}
@Override
public List findAll() {
log.info("Find All Executing");
List matterDetailsList = em.createNamedQuery("VMatterDetails.findAll")
.getResultList();
log.info("Find All Return");
return matterDetailsList;
}
@Override
public int count() {
throw new UnsupportedOperationException("Not supported yet.");
}
...
}但同样，这只是一个附注，这不会解决你的问题。
首先检查生成的SQL并使用结果更新您的问题。如果查询返回数据，请告诉我们如何检查bean方法不起作用。