十月 11, 2013 3:01:51 下午 org.hibernate.annotations.common.Version <clinit>
INFO: HCANN000001: Hibernate Commons Annotations {4.0.1.Final}
十月 11, 2013 3:01:51 下午 org.hibernate.Version logVersion
INFO: HHH000412: Hibernate Core {4.1.11.Final}
十月 11, 2013 3:01:51 下午 org.hibernate.cfg.Environment <clinit>
INFO: HHH000206: hibernate.properties not found
十月 11, 2013 3:01:51 下午 org.hibernate.cfg.Environment buildBytecodeProvider
INFO: HHH000021: Bytecode provider name : javassist
十月 11, 2013 3:01:51 下午 org.hibernate.cfg.Configuration configure
INFO: HHH000043: Configuring from resource: /hibernate.cfg.xml
十月 11, 2013 3:01:51 下午 org.hibernate.cfg.Configuration getConfigurationInputStream
INFO: HHH000040: Configuration resource: /hibernate.cfg.xml
十月 11, 2013 3:01:51 下午 org.hibernate.internal.util.xml.DTDEntityResolver resolveEntity
WARN: HHH000223: Recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!
十月 11, 2013 3:01:51 下午 org.hibernate.cfg.Configuration addResource
INFO: HHH000221: Reading mappings from resource: hbm/DhMaster.hbm.xml
十月 11, 2013 3:01:52 下午 org.hibernate.cfg.Configuration doConfigure
INFO: HHH000041: Configured SessionFactory: SessionFactory
十月 11, 2013 3:01:52 下午 org.hibernate.service.jdbc.connections.internal.DriverManagerConnectionProviderImpl configure
INFO: HHH000402: Using Hibernate built-in connection pool (not for production use!)
十月 11, 2013 3:01:52 下午 org.hibernate.service.jdbc.connections.internal.DriverManagerConnectionProviderImpl configure
INFO: HHH000115: Hibernate connection pool size: 20
十月 11, 2013 3:01:52 下午 org.hibernate.service.jdbc.connections.internal.DriverManagerConnectionProviderImpl configure
INFO: HHH000006: Autocommit mode: false
十月 11, 2013 3:01:52 下午 org.hibernate.service.jdbc.connections.internal.DriverManagerConnectionProviderImpl configure
INFO: HHH000401: using driver [oracle.jdbc.driver.OracleDriver] at URL [jdbc:oracle:thin:@localhost:1521:orcl]
十月 11, 2013 3:01:52 下午 org.hibernate.service.jdbc.connections.internal.DriverManagerConnectionProviderImpl configure
INFO: HHH000046: Connection properties: {user=wzh, password=****}
十月 11, 2013 3:01:52 下午 org.hibernate.dialect.Dialect <init>
INFO: HHH000400: Using dialect: org.hibernate.dialect.Oracle10gDialect
十月 11, 2013 3:01:52 下午 org.hibernate.engine.jdbc.internal.LobCreatorBuilder useContextualLobCreation
INFO: HHH000424: Disabling contextual LOB creation as createClob() method threw error : java.lang.reflect.InvocationTargetException
十月 11, 2013 3:01:52 下午 org.hibernate.engine.transaction.internal.TransactionFactoryInitiator initiateService
INFO: HHH000399: Using default transaction strategy (direct JDBC transactions)
十月 11, 2013 3:01:52 下午 org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory <init>
INFO: HHH000397: Using ASTQueryTranslatorFactory
十月 11, 2013 3:01:52 下午 org.hibernate.internal.SessionFactoryRegistry addSessionFactory
WARN: HHH000277: Could not bind factory to JNDI
org.hibernate.service.jndi.JndiException: Error parsing JNDI name [SessionFactory]
at org.hibernate.service.jndi.internal.JndiServiceImpl.parseName(JndiServiceImpl.java:92)
at org.hibernate.service.jndi.internal.JndiServiceImpl.bind(JndiServiceImpl.java:108)
at org.hibernate.internal.SessionFactoryRegistry.addSessionFactory(SessionFactoryRegistry.java:89)
at org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:478)
at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1742)
at wzh.main.util.HibernateSessionFactory.<clinit>(HibernateSessionFactory.java:34)
at basic.master.Test1.test(Test1.java:13)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
Caused by: javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:307)
at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:344)
at javax.naming.InitialContext.getNameParser(InitialContext.java:499)
at org.hibernate.service.jndi.internal.JndiServiceImpl.parseName(JndiServiceImpl.java:86)
... 29 more
以上异常是我在用eclipse-jee配置hibernate4是通过逆向工程创建了hibernate.cfg.xml文件,当创建了的xml文件中的<session-factory>元素多了一个name属性(也就是上面的name="SessionFactory"),就会报此错误,删除掉就行了!
分享到:
相关推荐
郁闷啊,有时候不得不承认,无论是什么事,曾经是好的,到后边未必还是好的,不要拿曾经的种种来判断今天的结果, 前景:之前本地用jeecg(1.7版本)设计流程、发布流程、修改流程,所有的操作都是项目有汉字启动的,...
2020-02-19 10:34:46.901 INFO 5920 --- [nio-8080-exec-1] o.apache.coyote.http11.Http11Processor : Error parsing HTTP request header Note: further occurrences of HTTP header parsing errors will be ...
4. 根据实际情况,编写处理错误的逻辑,如提示用户重新输入正确的数据,或者执行其他必要的错误恢复程序。 代码示例: ```python import json try: # 假设data是你的JSON字符串 data = '{"key":"value","another...
用于离开挂机行好挂机。你离开一下为了不让他人动你电脑就现在开始把
在PHP开发过程中,当遇到"PHP XML error parsing SOAP payload on line 1"的错误提示时,这通常意味着在解析SOAP消息体(payload)时遇到了XML编码问题。此问题的根源通常在于字符编码不匹配,特别是在涉及到多层...
解析错误(parsing_error)是在编程中经常遇到的问题,尤其是在处理数据时,例如解析JSON或XML文件。解决这类错误通常需要按照一定的步骤进行排查和修复。 首先,最常见的解析错误是由于代码语法不正确导致的。在...
Document Parsing Error(解决方案).md
直接复制到Notepad++ 安装目录下的\plugins文件夹即可 - 使用的时候全选json部分字符 - 在工具栏选择 -插件 --JSONviewer ---Format JSON 即可转换
Node Data Parsing Error(解决方案).md
Edge Data Parsing Error(解决方案).md
在处理网络请求和数据解析时,常见的错误之一是响应解析错误(Response Parsing Error)。这种错误通常发生在尝试将服务器响应的数据转换成特定格式(如JSON)的过程中。解析错误可能是由多种原因造成的,比如数据...
数据集包括:ATR(human parsing)、LIP(Looking into Person)、Multi-human-parsing数据集。基本山涵盖了所有国际公开的human parsing数据集!
print("Configuration Parsing Error:", e) # 打印错误信息,帮助定位问题所在 ``` 上述代码段展示了如何捕获解析异常并打印错误信息,这有助于用户快速定位问题。 对于处理更为复杂的配置文件,比如那些使用了...
4. 简化代码:在无法确定错误位置时,可以尝试逐步简化代码,去掉复杂的部分,保留核心逻辑,逐步调试,直至找到出错的具体位置。 5. 使用调试工具:一些集成开发环境(IDE)或代码编辑器提供了强大的调试工具,...
Error while parsing UI hierarchy XML file: null[Ljava.lang.StackTraceElement;@14b61ef4 Error while parsing UI hierarchy XML file: null[Ljava.lang.StackTraceElement;@14b61ef4
Parsing JSON in Swift will teach you to harness the power of Swift and give you confidence that your app can gracefully handle any JSON that comes its way. You'll learn: - How to use ...
根据给定文件的内容,我们今天要详细探讨的知识点是ArcGIS中的Python字段计算器(Python field calculator)。这个工具对于使用ArcGIS10版本的用户尤其重要,因为它提供了字段计算器只支持Python语言的解决方案,极...