Could not locate getter method for property [com.itcast.domain.Linkman#linkMans]

本文分析了Hibernate在进行实体关联映射时出现的具体异常及其原因,并提供了详细的解决步骤。通过调整XML配置文件中的属性名称,成功解决了由于getter方法未找到而导致的问题。

运行环境:jdk1.8 hibernate5.2

报错信息:

java.lang.ExceptionInInitializerError
    at com.itcast.test.Test1.run1(Test1.java:14)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:498)
    at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
    at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
    at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
    at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
    at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
    at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
    at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
    at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
    at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
    at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
    at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
    at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
    at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
    at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86)
    at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459)
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:678)
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382)
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192)
Caused by: org.hibernate.MappingException: Could not get constructor for org.hibernate.persister.entity.SingleTableEntityPersister
    at org.hibernate.persister.internal.PersisterFactoryImpl.createEntityPersister(PersisterFactoryImpl.java:123)
    at org.hibernate.persister.internal.PersisterFactoryImpl.createEntityPersister(PersisterFactoryImpl.java:77)
    at org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:346)
    at org.hibernate.boot.internal.SessionFactoryBuilderImpl.build(SessionFactoryBuilderImpl.java:444)
    at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:708)
    at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:724)
    at com.itcast.utils.HibernateUtils.<clinit>(HibernateUtils.java:22)
    ... 24 more
Caused by: org.hibernate.HibernateException: Unable to instantiate default tuplizer [org.hibernate.tuple.entity.PojoEntityTuplizer]
    at org.hibernate.tuple.entity.EntityTuplizerFactory.constructTuplizer(EntityTuplizerFactory.java:91)
    at org.hibernate.tuple.entity.EntityTuplizerFactory.constructDefaultTuplizer(EntityTuplizerFactory.java:116)
    at org.hibernate.tuple.entity.EntityMetamodel.<init>(EntityMetamodel.java:388)
    at org.hibernate.persister.entity.AbstractEntityPersister.<init>(AbstractEntityPersister.java:509)
    at org.hibernate.persister.entity.SingleTableEntityPersister.<init>(SingleTableEntityPersister.java:124)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
    at org.hibernate.persister.internal.PersisterFactoryImpl.createEntityPersister(PersisterFactoryImpl.java:96)
    ... 30 more
Caused by: java.lang.reflect.InvocationTargetException
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
    at org.hibernate.tuple.entity.EntityTuplizerFactory.constructTuplizer(EntityTuplizerFactory.java:88)
    ... 39 more
Caused by: org.hibernate.PropertyNotFoundException: Could not locate getter method for property [com.itcast.domain.Linkman#linkMans]
    at org.hibernate.internal.util.ReflectHelper.findGetterMethod(ReflectHelper.java:400)
    at org.hibernate.property.access.internal.PropertyAccessBasicImpl.<init>(PropertyAccessBasicImpl.java:41)
    at org.hibernate.property.access.internal.PropertyAccessStrategyBasicImpl.buildPropertyAccess(PropertyAccessStrategyBasicImpl.java:27)
    at org.hibernate.mapping.Property.getGetter(Property.java:299)
    at org.hibernate.tuple.entity.PojoEntityTuplizer.buildPropertyGetter(PojoEntityTuplizer.java:270)
    at org.hibernate.tuple.entity.AbstractEntityTuplizer.<init>(AbstractEntityTuplizer.java:145)
    at org.hibernate.tuple.entity.PojoEntityTuplizer.<init>(PojoEntityTuplizer.java:63)
    ... 44 more

看异常栈:主要原因是:
Could not locate getter method for property [com.itcast.domain.Linkman#linkMans]
就是找不到属性,是配置文件设置错误;

解决方案:解决方案:在/day30_/src/com/itcast/domain/Linkman.hbm.xml中

    <many-to-one name="customer" class="com.itcast.domain.Customer" column="lkm_cust_id"></many-to-one>
写成
    <many-to-one name="linkMans" class="com.itcast.domain.Customer" column="lkm_cust_id"></many-to-one>

改过来之后,重点来了,要重新部署tomcat,重启eclipse才有效

### 解决方案分析 当遇到 `Could not locate setup-boot-loader.bat` 错误时,通常表明构建环境中缺少必要的脚本文件或配置不正确。以下是可能的原因以及解决方案: #### 可能原因一:环境变量未设置 如果系统的路径中未包含该脚本所在的目录,则可能会导致此错误。需要确认 `setup-boot-loader.bat` 文件的实际位置并将其添加到系统 PATH 中[^1]。 ```batch set PATH=%PATH%;C:\path\to\your\scripts\ ``` #### 可能原因二:依赖项缺失 某些情况下,`setup-boot-loader.bat` 的运行依赖于其他库或工具的存在。例如,在使用 FFT 库时,还需要安装 `stb.lib` 工具集[^2]。因此,建议检查是否存在类似的依赖关系,并确保所有必需组件均已正确安装。 #### 可能原因三:重复打包问题 根据已知信息,重新打包现有的引导 JAR 文件可能导致不必要的依赖项被引入,从而引发各种兼容性问题[^3]。为了避免这种情况发生,可以尝试以下措施: - 验证当前项目是否确实需要重新创建引导加载程序。 - 如果不需要重新打包,则可以直接跳过相关步骤以减少潜在风险。 #### 替代方法 如果没有找到原始的 `setup-boot-loader.bat` 文件,可以通过手动编写一个简单的批处理脚本来替代其功能。下面是一个基本示例: ```batch @echo off :: 设置工作目录 cd /d %~dp0 :: 初始化参数 if "%JAVA_HOME%"=="" ( echo JAVA_HOME environment variable must be set. exit /b 1 ) :: 执行核心命令 "%JAVA_HOME%\bin\java.exe" -jar your-boot-jar-file.jar exit /b %ERRORLEVEL% ``` 请注意,上述代码仅为模板形式;实际应用前需调整具体选项以匹配目标需求。 --- ###
评论 1
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

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

抵扣说明:

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

余额充值