Hibernate retornando nenhum resultado mostra esta informação de erro: não vinculando fábrica a jndi, nenhum nome jndi configurado

Question

Estou usando o JPA com o Hibernate e tentando me conectar ao DataSource para recuperar informações, mas quando executo o aplicativo, não recebo nenhum erro como tal, mas nenhum resultado é exibido quando executo o seguinte código. A pergunta surgiu de uma postagem anterior localizada localizada aqui Quando eu estava configurando o ambiente para fazer alguns testes de JPA com hibernado no Glassfish.

O arquivo de log mostra isso

INFO: Not binding factory to JNDI, no JNDI name configured

Meu arquivo de log

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

O feijão EJB é

@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.");
    }

E minha persistência 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>

Answer 1

O tronco que você colou não mostra nenhum ERROR (nem FATAL nem WARNING) mensagem e a mensagem específica que você está mostrando está apenas dizendo que você não ligou o SessionFactory para jndi. Não há nada de errado nisso, muitos aplicativos não usam um Factory de sessão ligada a jndi E isso não é realmente relevante ao usar o JPA de qualquer maneira. Então, apenas ignore isso INFOMensagem rmacional.

Na verdade, de acordo com o arquivo de log, tudo parece bem: suas entidades foram detectadas, as consultas nomeadas processadas, o esquema foi atualizado (para que a conexão com o banco de dados esteja OK), etc.

Dito isto, eu primeiro ativaria o log do SQL para ver o que está acontecendo exatamente (isso não resolve o problema, mas ainda assim). Você pode definir definir a seguinte propriedade em seu persistence.xml:

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

Ou (e eu prefiro esta opção porque quero um bom controle sobre o log de qualquer maneira), definindo o nível de registro para depurar para a seguinte categoria:

org.hibernate.SQL

E execute o SQL gerado em relação ao banco de dados.

Segunda coisa, sugiro usar um injetado gerenciado por contêineres EntityManager Em vez de usar um aplicativo gerenciado EntityManager (Esse é o caminho preferido de seguir um ambiente gerenciado):

@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.");
    }
    ...
}

Mas, novamente, isso é apenas uma nota lateral, isso não resolverá seu problema.

Comece com a verificação do SQL gerado e atualize sua pergunta com o resultado. Se a consulta retornar dados, diga -nos como você verificou se o método Bean não funciona.

Referências

• Hibernate Core Documentation
  • 3.5. Exploração madeireira