Deprecated API
Contents
-
Terminally Deprecated ElementsElementDescriptionas of 5.2, along with
PropertyPlaceholderConfigurer; to be removed in 8.0as of 5.2, to be removed in 8.0; useorg.springframework.context.support.PropertySourcesPlaceholderConfigurerinstead which is more flexible through taking advantage of theEnvironmentandPropertySourcemechanisms.as of 7.1, in favor ofPropertyPath. UsePropertyPath.parse(String)andPropertyPath.canonicalName()in place ofPropertyAccessorUtils.canonicalPropertyName(String)andPropertyAccessorUtils.canonicalPropertyNames(String[]), and match a registered path against a property by comparing canonical names in place ofPropertyAccessorUtils.matchesProperty(String, String). There is no direct replacement forPropertyAccessorUtils.getPropertyName(String),PropertyAccessorUtils.isNestedOrIndexedProperty(String),PropertyAccessorUtils.getFirstNestedPropertySeparatorIndex(String), orPropertyAccessorUtils.getLastNestedPropertySeparatorIndex(String), which operate on raw, unparsed property path text.as severely outdated and superseded by more modern solutions, for example in Spring Data Commonsas severely outdated and superseded by more modern solutions, for example in Spring Data Commonsas severely outdated and superseded by more modern solutions, for example in Spring Data Commonsas severely outdated and superseded by more modern solutions, for example in Spring Data Commons
-
Deprecated InterfacesInterfaceDescriptionas severely outdated and superseded by more modern solutions, for example in Spring Data Commons
-
Deprecated ClassesClassDescriptionas of 5.2, along with
PropertyPlaceholderConfigurer; to be removed in 8.0as of 5.2, to be removed in 8.0; useorg.springframework.context.support.PropertySourcesPlaceholderConfigurerinstead which is more flexible through taking advantage of theEnvironmentandPropertySourcemechanisms.in favor of Spring's common bean definition formats and/or custom BeanDefinitionReader implementationsas of 7.1, in favor ofPropertyPath. UsePropertyPath.parse(String)andPropertyPath.canonicalName()in place ofPropertyAccessorUtils.canonicalPropertyName(String)andPropertyAccessorUtils.canonicalPropertyNames(String[]), and match a registered path against a property by comparing canonical names in place ofPropertyAccessorUtils.matchesProperty(String, String). There is no direct replacement forPropertyAccessorUtils.getPropertyName(String),PropertyAccessorUtils.isNestedOrIndexedProperty(String),PropertyAccessorUtils.getFirstNestedPropertySeparatorIndex(String), orPropertyAccessorUtils.getLastNestedPropertySeparatorIndex(String), which operate on raw, unparsed property path text.as severely outdated and superseded by more modern solutions, for example in Spring Data Commonsas severely outdated and superseded by more modern solutions, for example in Spring Data Commonsas severely outdated and superseded by more modern solutions, for example in Spring Data Commons
-
Deprecated FieldsFieldDescriptionIf you are using mixed autowiring strategies, prefer annotation-based autowiring for clearer demarcation of autowiring needs.If you are using mixed autowiring strategies, use annotation-based autowiring for clearer demarcation of autowiring needs.
-
Deprecated MethodsMethodDescriptionfollowing the deprecation of
Class.newInstance()in JDK 9as of 6.1, in favor of implicit post-processing throughAutowireCapableBeanFactory.initializeBean(Object, String)as of 6.1, in favor of implicit post-processing throughAutowireCapableBeanFactory.initializeBean(Object, String)in favor ofAutowireCapableBeanFactory.createBean(Class)as of 6.2, in favor of lenient singleton locking (with this method returning an arbitrary object to lock on)in favor ofRegisteredBean.resolveInstantiationDescriptor()
-
Deprecated ConstructorsConstructorDescriptionas of 6.0.11, in favor of an extra
RootBeanDefinition.setTargetType(ResolvableType)call