2

休止状態で JPA を使用し、データソースに接続して情報を取得しようとしていますが、アプリケーションを実行してもエラーは発生しませんが、次のコードを実行しても結果は表示されません。 Glassfishで休止状態を使用して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>
4

1 に答える 1

2

貼り付けたログにはERROR（FATALまたは）メッセージは表示されず、表示されている特定のメッセージは、をJNDIにWARNINGバインドしなかったことを示しているだけです。SessionFactoryこれには何の問題もありません。多くのアプリケーションはJNDIにバインドされたSessionFactoryを使用せず、とにかくJPAを使用する場合はこれは実際には関係ありません。したがって、このINFOrmationalメッセージは無視してください。

実際、ログファイルによると、すべてが正常に見えます。エンティティが検出された、名前付きクエリが処理された、スキーマが更新された（DBへの接続がOK）などです。

そうは言っても、最初にSQLロギングをアクティブにして、何が起こっているかを正確に確認します（これでは問題は解決しませんが、それでも問題は解決しません）。次のプロパティを設定することができますpersistence.xml：

<!-- Echo all executed SQL to stdout -->
<property name="hibernate.show_sql" value="true"/>

または（とにかくログを細かく制御したいので、このオプションを好みます）、次のカテゴリのデバッグにログレベルを設定します。

org.hibernate.SQL

そして、生成されたSQLをデータベースに対して実行します。

次に、管理対象のアプリケーションを使用する代わりに、注入されたコンテナー管理対象EntityManagerEntityManagerを使用することをお勧めします（これは、管理対象環境で使用するための推奨される方法です）。

@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メソッドが機能しないことをどのように確認したかを教えてください。

参考文献

于 2010-09-03T02:20:13.950 に答える