Consistently use constructor-based instantiation instead of Class.newInstance / BeanUtils.instantiate
Issue: SPR-14486
This commit is contained in:
@@ -1,5 +1,5 @@
|
||||
/*
|
||||
* Copyright 2002-2014 the original author or authors.
|
||||
* Copyright 2002-2016 the original author or authors.
|
||||
*
|
||||
* Licensed under the Apache License, Version 2.0 (the "License");
|
||||
* you may not use this file except in compliance with the License.
|
||||
@@ -59,7 +59,7 @@ public class JtaTransactionManagerFactoryBean implements FactoryBean<JtaTransact
|
||||
try {
|
||||
Class<? extends JtaTransactionManager> clazz = (Class<? extends JtaTransactionManager>)
|
||||
ClassUtils.forName(className, JtaTransactionManagerFactoryBean.class.getClassLoader());
|
||||
this.transactionManager = BeanUtils.instantiate(clazz);
|
||||
this.transactionManager = BeanUtils.instantiateClass(clazz);
|
||||
}
|
||||
catch (ClassNotFoundException ex) {
|
||||
throw new IllegalStateException("Failed to load JtaTransactionManager class: " + className, ex);
|
||||
|
||||
Reference in New Issue
Block a user