kapok

垃圾桶,嘿嘿,我藏的这么深你们还能找到啊,真牛!

  BlogJava :: 首页 :: 新随笔 :: 联系 :: 聚合  :: 管理 ::
  455 随笔 :: 0 文章 :: 76 评论 :: 0 Trackbacks

/*
 * Copyright 2002-2005 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.
 * You may obtain a copy of the License at
 *
 *      http://www.apache.org/licenses/LICENSE-2.0
 *
 * Unless required by applicable law or agreed to in writing, software
 * distributed under the License is distributed on an "AS IS" BASIS,
 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 * See the License for the specific language governing permissions and
 * limitations under the License.
 */

package org.springframework.beans.factory;

import org.springframework.beans.BeansException;

/**
 * The root interface for accessing a Spring IoC container.
 *
 * <p>This interface is implemented by objects that hold a number of bean definitions,
 * each uniquely identified by a String name. Depending on the bean definition,
 * the factory will return either an independent instance of a
 * contained object (the Prototype design pattern), or a single
 * shared instance (a superior alternative to the Singleton
 * design pattern, in which the instance is a singleton in the scope of
 * the factory). Which type of instance will be returned depends on the bean
 * factory configuration - the API is the same. The Singleton approach is
 * more useful and more common in practice.
 *
 * <p>The point of this approach is that the BeanFactory is a central registry
 * of application components, and centralizes configuration of application
 * components (no more do individual objects need to read properties files,
 * for example). See chapters 4 and 11 of "Expert One-on-One J2EE Design and
 * Development" for a discussion of the benefits of this approach.
 *
 * <p>Note that it is generally better to rely on Dependency Injection
 * ("push" configuration) to configure application objects through setters
 * or constructors, rather than use
 * any form of "pull" configuration like a BeanFactory lookup. Spring's
 * Dependency Injection functionality is implemented using BeanFactory
 * and its subinterfaces.
 *
 * <p>Normally a BeanFactory will load bean definitions stored in a configuration
 * source (such as an XML document), and use the org.springframework.beans package
 * to configure the beans. However, an implementation could simply return Java
 * objects it creates as necessary directly in Java code. There are no constraints
 * on how the definitions could be stored: LDAP, RDBMS, XML, properties file etc.
 * Implementations are encouraged to support references amongst beans, to either
 * Singletons or Prototypes.
 *
 * <p>In contrast to the methods in ListableBeanFactory, all of the methods in this
 * interface will also check parent factories if this is a HierarchicalBeanFactory.
 * If a bean is not found in this factory instance, the immediate parent is asked.
 * Beans in this factory instance are supposed to override beans of the same name
 * in any parent factory.
 *
 * <p>Bean factory implementations should support the standard bean lifecycle interfaces
 * as far as possible. The maximum set of initialization methods and their standard
 * order is:<br>
 * 1. BeanNameAware's setBeanName<br>
 * 2. BeanFactoryAware's setBeanFactory<br>
 * 3. ApplicationContextAware's setApplicationContext (only applicable if running
 * in an application context)<br>
 * 4. postProcessBeforeInitialization methods of BeanPostProcessors<br>
 * 5. InitializingBean's afterPropertiesSet<br>
 * 6. a custom init-method definition<br>
 * 7. postProcessAfterInitialization methods of BeanPostProcessors
 *
 * <p>On shutdown of a bean factory, the following lifecycle methods apply:<br>
 * 1. DisposableBean's destroy<br>
 * 2. a custom destroy-method definition
 *
 * @author Rod Johnson
 * @author Juergen Hoeller
 * @since 13 April 2001
 * @see BeanNameAware#setBeanName
 * @see BeanFactoryAware#setBeanFactory
 * @see InitializingBean#afterPropertiesSet
 * @see DisposableBean#destroy
 * @see org.springframework.beans.factory.config.BeanPostProcessor#postProcessBeforeInitialization
 * @see org.springframework.beans.factory.config.BeanPostProcessor#postProcessAfterInitialization
 * @see org.springframework.beans.factory.support.RootBeanDefinition#getInitMethodName
 * @see org.springframework.beans.factory.support.RootBeanDefinition#getDestroyMethodName
 * @see org.springframework.context.ApplicationContextAware#setApplicationContext
 */
public interface BeanFactory {

 /**
  * Used to dereference a FactoryBean and distinguish it from beans
  * <i>created</i> by the FactoryBean. For example, if the bean named
  * <code>myEjb</code> is a FactoryBean, getting <code>&myEjb</code> will
  * return the factory, not the instance returned by the factory.
  */
 String FACTORY_BEAN_PREFIX = "&";


 /**
  * Return an instance, which may be shared or independent, of the given bean name.
  * This method allows a Spring bean factory to be used as a replacement for
  * the Singleton or Prototype design pattern.
  * <p>Callers may retain references to returned objects
  * in the case of Singleton beans.
  * <p>This method delegates to the parent factory if the
  * bean cannot be found in this factory instance.
  * @param name the name of the bean to return
  * @return the instance of the bean
  * @throws NoSuchBeanDefinitionException if there is no bean definition
  * with the specified name
  * @throws BeansException if the bean could not be obtained
  */
 Object getBean(String name) throws BeansException;

 /**
  * Return an instance (possibly shared or independent) of the given bean name.
  * <p>Behaves the same as getBean(String), but provides a measure of type safety by
  * throwing a Spring BeansException if the bean is not of the required type.
  * This means that ClassCastException can't be thrown on casting the result correctly,
  * as can happen with getBean(String).
  * @param name the name of the bean to return
  * @param requiredType type the bean must match. Can be an interface or superclass
  * of the actual class, or null for any match. For example, if the value is
  * Object.class, this method will succeed whatever the class of the returned instance.
  * @return an instance of the bean (never null)
  * @throws BeanNotOfRequiredTypeException if the bean is not of the required type
  * @throws NoSuchBeanDefinitionException if there's no such bean definition
  * @throws BeansException if the bean could not be created
  */
 Object getBean(String name, Class requiredType) throws BeansException;

 /**
  * Does this bean factory contain a bean definition with the given name?
  * <p>Will ask the parent factory if the bean cannot be found in this factory instance.
  * @param name the name of the bean to query
  * @return whether a bean with the given name is defined
  */
 boolean containsBean(String name);

 /**
  * Is this bean a singleton? That is, will getBean() always return the same object?
  * <p>Will ask the parent factory if the bean cannot be found in this factory instance.
  * @param name the name of the bean to query
  * @return is this bean a singleton
  * @throws NoSuchBeanDefinitionException if there is no bean with the given name
  */
 boolean isSingleton(String name) throws NoSuchBeanDefinitionException;

 /**
  * Determine the type of the bean with the given name.
  * More specifically, checks the type of object that getBean would return.
  * For a FactoryBean, returns the type of object that the FactoryBean creates.
  * @param name the name of the bean to query
  * @return the type of the bean, or null if not determinable
  * @throws NoSuchBeanDefinitionException if there is no bean with the given name
  * @since 1.1.2
  * @see #getBean
  * @see FactoryBean#getObjectType
  */
 Class getType(String name) throws NoSuchBeanDefinitionException;

 /**
  * Return the aliases for the given bean name, if defined.
  * <p>Will ask the parent factory if the bean cannot be found in this factory instance.
  * @param name the bean name to check for aliases
  * @return the aliases, or an empty array if none
  * @throws NoSuchBeanDefinitionException if there's no such bean definition
  */
 String[] getAliases(String name) throws NoSuchBeanDefinitionException;

}

posted on 2005-05-06 00:43 笨笨 阅读(522) 评论(0)  编辑  收藏 所属分类: J2EEHibernateAndSpringALL

只有注册用户登录后才能发表评论。


网站导航: