亚洲必赢手机ssh框架遇到的问题总。ssh框架遇到的题材总。

by admin on 2018年10月18日

1.org.springframework.beans.factory.BeanCreationException: Error
creating bean with name ‘dataSource’ defined in class path resource
[applicationContext.xml]: Error setting property values; nested
exception is org.springframework.beans.NotWritablePropertyException:
Invalid property ‘driverName’ of bean class
[com.mchange.v2.c3p0.ComboPooledDataSource]: Bean property
‘driverName’ is not writable or has an invalid setter method. Does the
parameter type of the setter match the return type of the getter?

1.org.springframework.beans.factory.BeanCreationException: Error
creating bean with name ‘dataSource’ defined in class path resource
[applicationContext.xml]: Error setting property values; nested
exception is org.springframework.beans.NotWritablePropertyException:
Invalid property ‘driverName’ of bean class
[com.mchange.v2.c3p0.ComboPooledDataSource]: Bean property
‘driverName’ is not writable or has an invalid setter method. Does the
parameter type of the setter match the return type of the getter?

Caused by: org.springframework.beans.NotWritablePropertyException:
Invalid property ‘driverName’ of bean class
[com.mchange.v2.c3p0.ComboPooledDataSource]: Bean property
‘driverName’ is not writable or has an invalid setter method. Does the
parameter type of the setter match the return type of the getter?
不当翻译过来就是:driverClassName 称我
com.mchange.v2.c3p0.ComboPooledDataSource勿服气得,改个自我认的,不然我罢工
解决:改名
driverClassName –>driverClass
url –>jdbcUrl
username –>user
password—>password

Caused by: org.springframework.beans.NotWritablePropertyException:
Invalid property ‘driverName’ of bean class
[com.mchange.v2.c3p0.ComboPooledDataSource]: Bean property
‘driverName’ is not writable or has an invalid setter method. Does the
parameter type of the setter match the return type of the getter?
张冠李戴翻译过来就是是:driverClassName 号称我
com.mchange.v2.c3p0.ComboPooledDataSource非认得,改个自己认识的,不然我罢工
解决:改名
driverClassName –>driverClass
url –>jdbcUrl
username –>user
password—>password

2.Caused by: java.lang.NoClassDefFoundError:
javax/transaction/SystemException
解决:确少geronimo-jta jar包

2.Caused by: java.lang.NoClassDefFoundError:
javax/transaction/SystemException
解决:确少geronimo-jta jar包

 

 

3.Caused by: org.springframework.beans.PropertyBatchUpdateException;
nested PropertyAccessExceptions (1) are:
PropertyAccessException 1:
org.springframework.beans.MethodInvocationException: Property
‘dataSource’ threw exception; nested exception is
java.lang.NoClassDefFoundError:
org/springframework/jdbc/datasource/TransactionAwareDataSourceProxy
解决:<!– 配置事务 –>
<bean id=”transactionManager”
class=”org.springframework.orm.hibernate5.HibernateTransactionManager”>
<property name=”dataSource”
ref=”dataSource”></property>//这里并非为此dataSource.改用sessionFactory
</bean>

3.Caused by: org.springframework.beans.PropertyBatchUpdateException;
nested PropertyAccessExceptions (1) are:
PropertyAccessException 1:
org.springframework.beans.MethodInvocationException: Property
‘dataSource’ threw exception; nested exception is
java.lang.NoClassDefFoundError:
org/springframework/jdbc/datasource/TransactionAwareDataSourceProxy
解决:<!– 配置事务 –>
<bean id=”transactionManager”
class=”org.springframework.orm.hibernate5.HibernateTransactionManager”>
<property name=”dataSource”
ref=”dataSource”></property>//这里并非为此dataSource.改用sessionFactory
</bean>

4.Caused by: java.lang.ClassNotFoundException:
org.springframework.jdbc.datasource.TransactionAwareDataSourceProxy
解决:确少spring-jdbc-4.2.4.RELEASE.jar包

4.Caused by: java.lang.ClassNotFoundException:
org.springframework.jdbc.datasource.TransactionAwareDataSourceProxy
解决:确少spring-jdbc-4.2.4.RELEASE.jar包

5.HTTP Status 500 – Write operations are not allowed in read-only mode
(FlushMode.MANUAL): Turn your Session into FlushMode.COMMIT/AUTO or
remove ‘readOnly’ marker from transaction definition.
严重: Exception occurred during processing request: Write operations are
not allowed in read-only mode (FlushMode.MANUAL): Turn your Session into
FlushMode.COMMIT/AUTO or remove ‘readOnly’ marker from transaction
definition.
org.springframework.dao.InvalidDataAccessApiUsageException: Write
operations are not allowed in read-only mode (FlushMode.MANUAL): Turn
your Session into FlushMode.COMMIT/AUTO or remove ‘readOnly’ marker from
transaction definition.

5.HTTP Status 500 – Write operations are not allowed in read-only mode
(FlushMode.MANUAL): Turn your Session into FlushMode.COMMIT/AUTO or
remove ‘readOnly’ marker from transaction definition.
严重: Exception occurred during processing request: Write operations are
not allowed in read-only mode (FlushMode.MANUAL): Turn your Session into
FlushMode.COMMIT/AUTO or remove ‘readOnly’ marker from transaction
definition.
org.springframework.dao.InvalidDataAccessApiUsageException: Write
operations are not allowed in read-only mode (FlushMode.MANUAL): Turn
your Session into FlushMode.COMMIT/AUTO or remove ‘readOnly’ marker from
transaction definition.

缓解:在service的类及长@Transactional注解

釜底抽薪:在service的切近及添加@Transactional注解

6.Bean ‘sessionFactory’; nested exception is
org.springframework.beans.factory.parsing.BeanDefinitionParsingException:
Configuration problem: Tag ‘property’ must have a ‘name’ attribute
Offending resource: class path resource [applicationContext.xml]
Caused by:
org.springframework.beans.factory.parsing.BeanDefinitionParsingException:
Configuration problem: Tag ‘property’ must have a ‘name’ attribute
Offending resource: class path resource [applicationContext.xml]

6.Bean ‘sessionFactory’; nested exception is
org.springframework.beans.factory.parsing.BeanDefinitionParsingException:
Configuration problem: Tag ‘property’ must have a ‘name’ attribute
Offending resource: class path resource [applicationContext.xml]
Caused by:
org.springframework.beans.factory.parsing.BeanDefinitionParsingException:
Configuration problem: Tag ‘property’ must have a ‘name’ attribute
Offending resource: class path resource [applicationContext.xml]

解决:<!– 配置hibernate映射文件 –>时<property
name=””>的价值忘记写了

解决:<!– 配置hibernate映射文件 –>时<property
name=””>的价值忘记写了

7.Caused by: java.lang.ClassNotFoundException:
com.mchange.v2.ser.Indirector”
解决:缺少mchange-commons-java-0.2.3.4.jar

7.Caused by: java.lang.ClassNotFoundException:
com.mchange.v2.ser.Indirector”
解决:缺少mchange-commons-java-0.2.3.4.jar

8.java.lang.ClassNotFoundException: com.mysql.jdbc.Driver
解决:缺少mysql驱动jar包

8.java.lang.ClassNotFoundException: com.mysql.jdbc.Driver
解决:缺少mysql驱动jar包

9.Could not load requested class : com.ssh.entity.User
化解:因为pojo里的文本,xml的公文以及数据库里之公文里的照射出题目

9.Could not load requested class : com.ssh.entity.User
釜底抽薪:因为pojo里的文本,xml的文本及数据库里之公文里的映照出题目

Caused by: org.springframework.aop.framework.AopConfigException: Cannot
proxy target class because CGLIB2 is not available. Add CGLIB to the
class path or specify proxy interfaces.
解决:可能jar包重复也可能不够cglib-2.1.3.jar

Caused by: org.springframework.aop.framework.AopConfigException: Cannot
proxy target class because CGLIB2 is not available. Add CGLIB to the
class path or specify proxy interfaces.
化解:可能jar包重复也说不定不够cglib-2.1.3.jar

10.No result defined for action com.ssh.action.UserAction and result
success
缓解:是Struts.xml配置问题

10.No result defined for action com.ssh.action.UserAction and result
success
解决:是Struts.xml配置问题

11.Caused by: org.hibernate.hql.internal.ast.QuerySyntaxException: Emp
is not mapped [from Emp]
化解:applicationContext中从不加载*.hbm.xml映射文件

11.Caused by: org.hibernate.hql.internal.ast.QuerySyntaxException: Emp
is not mapped [from Emp]
缓解:applicationContext中从未加载*.hbm.xml映射文件

12.Caused by: org.hibernate.boot.MappingException: Association
[com.ssh.entity.Dept.setEmp] references an unmapped entity
[com.ssh.entity.Dept.setEmp] : origin(null)

12.Caused by: org.hibernate.boot.MappingException: Association
[com.ssh.entity.Dept.setEmp] references an unmapped entity
[com.ssh.entity.Dept.setEmp] : origin(null)

釜底抽薪:是xxx.hbm.xml中<class name=”com.ssh.entity.User”
table=”user”>name中之路子应该是xxx实体类的不二法门,结果写及其它的实体类的途径了

缓解:是xxx.hbm.xml中<class name=”com.ssh.entity.User”
table=”user”>name中之门路应该是xxx实体类的门路,结果写到其它的实体类的路线了

13.Caused by: org.springframework.beans.factory.BeanCreationException:
Error creating bean with name ‘deptDaoImpl’ defined in class path
resource [applicationContext.xml]: Error setting property values;
nested exception is
org.springframework.beans.NotWritablePropertyException: Invalid property
‘sessionFactory’ of bean class [com.ssh.dao.impl.DeptDaoImpl]: Bean
property ‘sessionFactory’ is not writable or has an invalid setter
method. Does the parameter type of the setter match the return type of
the getter?
缓解:没有依赖注入

13.Caused by: org.springframework.beans.factory.BeanCreationException:
Error creating bean with name ‘deptDaoImpl’ defined in class path
resource [applicationContext.xml]: Error setting property values;
nested exception is
org.springframework.beans.NotWritablePropertyException: Invalid property
‘sessionFactory’ of bean class [com.ssh.dao.impl.DeptDaoImpl]: Bean
property ‘sessionFactory’ is not writable or has an invalid setter
method. Does the parameter type of the setter match the return type of
the getter?
解决:没有借助注入

14.严重: Servlet.service() for servlet [jsp] threw exception
javax.el.PropertyNotFoundException: Property [id] not found on type
[java.lang.String]

14.严重: Servlet.service() for servlet [jsp] threw exception
javax.el.PropertyNotFoundException: Property [id] not found on type
[java.lang.String]

缓解:jsp中输出的id与实体类的eid不同等<c:forEach items=”list”
var=”emp”>或者是<c:forEach items=”list”
var=”emp”>items中应有写成${list }
<td>${emp.id }</td>

化解:jsp中输出的id与实体类的eid不一致<c:forEach items=”list”
var=”emp”>或者是<c:forEach items=”list”
var=”emp”>items中应该写成${list }
<td>${emp.id }</td>

15.Caused by: org.hibernate.MappingException: Duplicate property mapping
of ename found in com.ssh.entity.Emp
釜底抽薪:xxx.hbm.xml映射文件被来重复字段

15.Caused by: org.hibernate.MappingException: Duplicate property mapping
of ename found in com.ssh.entity.Emp
缓解:xxx.hbm.xml映射文件中发生再字段

16.HTTP Status 500 – not-null property references a null or transient
value : com.ssh.entity.Emp.esex; nested exception is
org.hibernate.PropertyValueException: not-null property references a
null or transient value : com.ssh.entity.Emp.esex
釜底抽薪:是xxx.hbm.xml中的特性设置也非能够也空,但是自己前台表单中的数填充为空了。

16.HTTP Status 500 – not-null property references a null or transient
value : com.ssh.entity.Emp.esex; nested exception is
org.hibernate.PropertyValueException: not-null property references a
null or transient value : com.ssh.entity.Emp.esex
缓解:是xxx.hbm.xml中的特性设置为非能够啊空,但是本人前台表单中的多寡填为空了。

17.org.springframework.beans.factory.parsing.BeanDefinitionParsingException:
Configuration problem: Unnamed bean definition specifies neither ‘class’
nor ‘parent’ nor ‘factory-bean’ – can’t generate bean name
Offending resource: class path resource [springmvc.xml]
釜底抽薪:由于:bean
没有配置一体化,少了class等性能之安排或者配置了拖欠的bean<bean></bean>

17.org.springframework.beans.factory.parsing.BeanDefinitionParsingException:
Configuration problem: Unnamed bean definition specifies neither ‘class’
nor ‘parent’ nor ‘factory-bean’ – can’t generate bean name
Offending resource: class path resource [springmvc.xml]
化解:由于:bean
没有安排一体化,少了class等特性的配备或者安排了空的bean<bean></bean>

18.java.lang.IllegalArgumentException: Expected
MultipartHttpServletRequest: is a MultipartResolver configured?
解决:这是坐找不顶multipartReslover的由,在springMVC配置文件配置它的时光,不克因此别样名字,只能用指定名字id=”multipartResolver”,否则即起这种找不至的一无是处。

18.java.lang.IllegalArgumentException: Expected
MultipartHttpServletRequest: is a MultipartResolver configured?
釜底抽薪:这是以找不顶multipartReslover的原委,在springMVC配置文件配置它的当儿,不能够用其他名字,只能用指定名字id=”multipartResolver”,否则就是应运而生这种找不至之荒谬。

Caused by: 元素类型为 “struts” 的情必须配合配
“((package|include|bean|constant)*,unknown-handler-stack?)”。 –
file:/E:/JavaDeveleper/apache-tomcat-9.0.0.M22/webapps/shop/WEB-INF/classes/struts.xml:17:10
缓解:Struts.xml配置文件被的action要描写在package中

Caused by: 元素类型为 “struts” 的始末要配合配
“((package|include|bean|constant)*,unknown-handler-stack?)”。 –
file:/E:/JavaDeveleper/apache-tomcat-9.0.0.M22/webapps/shop/WEB-INF/classes/struts.xml:17:10
解决:Struts.xml配置文件中之action要写以package中

19.java.lang.NoSuchMethodException:
com.opensymphony.xwork2.ActionSupport.listAll()
缓解:spring.xml核心配置文件忘记配置于应类的Javabean实例化

19.java.lang.NoSuchMethodException:
com.opensymphony.xwork2.ActionSupport.listAll()
釜底抽薪:spring.xml核心配置文件忘记配置为应类的Javabean实例化

20.Caused by: Action class [userAction] not found – action –
file:/C:/Users/smfx1314/workspace/.metadata/.plugins/org.eclipse.wst.server.core/tmp0/wtpwebapps/sshtest/WEB-INF/classes/struts.xml:7:63
java.lang.NoSuchMethodException: com.ssh.action.UserAction.save()

20.Caused by: Action class [userAction] not found – action –
file:/C:/Users/smfx1314/workspace/.metadata/.plugins/org.eclipse.wst.server.core/tmp0/wtpwebapps/sshtest/WEB-INF/classes/struts.xml:7:63
java.lang.NoSuchMethodException: com.ssh.action.UserAction.save()

缓解:原因是欠jar包:struts2-spring-plugin-2.1.8.jar要清理缓存,project

化解:原因是不够jar包:struts2-spring-plugin-2.1.8.jar还是清理缓存,project

21.There is no Action mapped for namespace [/] and action name
[delete] associated with context path [/sshtest]. – [unknown
location]
解决:Struts.xml中之action方法运用的是user_*的章程,在jsp页面中或其它请求被无按user_*的法要,加上前缀user就可了

21.There is no Action mapped for namespace [/] and action name
[delete] associated with context path [/sshtest]. – [unknown
location]
缓解:Struts.xml中之action方法以的凡user_*的艺术,在jsp页面中要么另请求被从来不以user_*的方法呼吁,加上前缀user就可以了

相关文章

发表评论

电子邮件地址不会被公开。 必填项已用*标注

网站地图xml地图