站内搜索: 请输入搜索关键词
当前页面: 在线文档首页 > Spring Framework 1.2.9 API 文档英文版

Deprecated List (Spring Framework) - Spring Framework 1.2.9 API 文档英文版


Deprecated API


Contents
Deprecated Interfaces
org.springframework.web.bind.BindInitializer
          since Spring 1.2.7: prefer direct ServletRequestDataBinder usage, potentially in combination with a PropertyEditorRegistrar 
org.springframework.validation.PropertyEditorRegistrar
          since Spring 1.2.6, in favor of the PropertyEditorRegistrar interface in the org.springframework.beans package 
 

Deprecated Classes
org.springframework.aop.target.AbstractLazyInitTargetSource
          since Spring 1.2.7: use AbstractLazyCreationTargetSource instead 
org.springframework.aop.interceptor.AbstractPerformanceMonitorInterceptor
          since Spring 1.2.7: use AbstractMonitoringInterceptor instead 
org.springframework.beans.factory.access.BeanFactoryBootstrap
          since Spring 1.2.7: consider using a BeanFactoryLocator or a custom bootstrap class instead 
org.springframework.web.bind.BindUtils
          since Spring 1.2.7: prefer direct ServletRequestDataBinder usage, potentially in combination with a PropertyEditorRegistrar 
org.springframework.context.event.ConsoleListener
          since Spring 1.2.7: doesn't serve any purpose 
org.springframework.web.servlet.view.xslt.FormatHelper
          as of Spring 1.2.9; to be removed 
org.springframework.aop.interceptor.TraceInterceptor
          since Spring 1.2: in favor of SimpleTraceInterceptor 
 

Deprecated Fields
org.springframework.core.io.support.ResourcePatternResolver.CLASSPATH_URL_PREFIX
          as of Spring 1.2.2, in favor of CLASSPATH_ALL_URL_PREFIX (to avoid shadowing the constant of the same name in ResourceLoader) 
 

Deprecated Methods
org.springframework.mock.web.MockHttpServletRequest.addRole(String)
          in favor of addUserRole 
org.springframework.beans.factory.BeanFactoryUtils.beanNamesIncludingAncestors(ListableBeanFactory, Class)
          in favor of beanNamesForTypeIncludingAncestors. This method will be removed as of Spring 2.0. 
org.springframework.beans.BeanUtils.canonicalName(String)
          as of Spring 1.2.9, in favor of PropertyAccessorUtils.canonicalPropertyName(String) 
org.springframework.jdbc.core.support.JdbcDaoSupport.closeConnectionIfNecessary(Connection)
          in favor of releaseConnection 
org.springframework.jdbc.datasource.DataSourceUtils.closeConnectionIfNecessary(Connection, DataSource)
          in favor of releaseConnection 
org.springframework.orm.ojb.support.PersistenceBrokerDaoSupport.closePersistenceBrokerIfNecessary(PersistenceBroker)
          in favor of releasePersistenceBroker 
org.springframework.orm.ojb.OjbFactoryUtils.closePersistenceBrokerIfNecessary(PersistenceBroker, PBKey)
          in favor of releasePersistenceBroker 
org.springframework.orm.jdo.support.JdoDaoSupport.closePersistenceManagerIfNecessary(PersistenceManager)
          in favor of releasePersistenceManager 
org.springframework.orm.jdo.PersistenceManagerFactoryUtils.closePersistenceManagerIfNecessary(PersistenceManager, PersistenceManagerFactory)
          in favor of releasePersistenceManager 
org.springframework.orm.hibernate3.support.HibernateDaoSupport.closeSessionIfNecessary(Session)
          in favor of HibernateDaoSupport.releaseSession(org.hibernate.Session) 
org.springframework.orm.hibernate.support.HibernateDaoSupport.closeSessionIfNecessary(Session)
          in favor of HibernateDaoSupport.releaseSession(net.sf.hibernate.Session) 
org.springframework.orm.hibernate.SessionFactoryUtils.closeSessionIfNecessary(Session, SessionFactory)
          in favor of releaseSession 
org.springframework.orm.hibernate3.SessionFactoryUtils.closeSessionIfNecessary(Session, SessionFactory)
          in favor of releaseSession 
org.springframework.web.servlet.view.xslt.AbstractXsltView.createDomNode(Map, String, HttpServletRequest, HttpServletResponse)
          in favor of createXsltSource(Map, String, HttpServletRequest, HttpServletResponse) 
org.springframework.web.servlet.view.xslt.AbstractXsltView.doTransform(Map, Node, HttpServletRequest, HttpServletResponse)
          the preferred method is doTransform with a Source argument 
org.springframework.web.servlet.view.xslt.AbstractXsltView.doTransform(Node, Map, Result, String)
          the preferred method is doTransform(Source source, Map parameters, Result result, String encoding) 
org.springframework.beans.factory.ListableBeanFactory.getBeanDefinitionNames(Class)
          in favor of getBeanNamesForType. This method will be removed as of Spring 2.0. 
org.springframework.web.servlet.view.document.AbstractPdfView.getDocument()
          in favor of newDocument 
org.springframework.web.servlet.mvc.AbstractWizardFormController.isCancel(HttpServletRequest)
          in favor of isCancelRequest 
org.springframework.web.servlet.mvc.AbstractWizardFormController.isFinish(HttpServletRequest)
          in favor of isFinishRequest 
org.springframework.ui.jasperreports.JasperReportsUtils.render(JRAbstractExporter, JasperPrint, OutputStream)
          in favor of the render version with JRExporter parameter 
org.springframework.ui.jasperreports.JasperReportsUtils.render(JRAbstractExporter, JasperPrint, Writer)
          in favor of the render version with JRExporter parameter 
org.springframework.context.support.ResourceBundleMessageSource.setClassLoader(ClassLoader)
          in favor of setBundleClassLoader 
org.springframework.jdbc.support.JdbcUtils.translateType(int)
          This is only used by deprecated constructors in SqlFunction and will be removed alongside those constructors. 
 

Deprecated Constructors
org.springframework.jdbc.object.SqlFunction(DataSource, String, int)
          Use the constructor with a result type Class instead. Note that the current version of SqlFunction will be able to guess the correct result type in my cases, so you often don't even need to specifiy the result type explicitly. 
org.springframework.jdbc.object.SqlFunction(DataSource, String, int[], int)
          Use the constructor with a result type Class instead. Note that the current version of SqlFunction will be able to guess the correct result type in my cases, so you often don't even need to specifiy the result type explicitly. 
 



Copyright (c) 2002-2007 The Spring Framework Project.