ApplicationContext as well. This chapter is divided into two parts, with the first part covering the basic principles that apply to both the BeanFactory and ApplicationContext, and with the second part covering those or the AOP Alliance API: Spring AOP remains backward-compatible. See the following chapter for a discussion of the Spring AOP APIs. Note One of the central tenets of the Spring Framework is that of non-invasiveness; See the section entitled Section 6.4, “Choosing which AOP declaration style to use” for a fuller discussion of the whys and wherefores of each style. 6.1.3. AOP Proxies Spring AOP defaults to using standard

ApplicationContext as well. This chapter is divided into two parts, with the first part covering the basic principles that apply to both the BeanFactory and ApplicationContext, and with the second part covering those or the AOP Alliance API: Spring AOP remains backward-compatible. See the following chapter for a discussion of the Spring AOP APIs. Note One of the central tenets of the Spring Framework is that of non-invasiveness; See the section entitled Section 6.4, “Choosing which AOP declaration style to use” for a fuller discussion of the whys and wherefores of each style. 6.1.3. AOP Proxies Spring AOP defaults to using standard

ApplicationContext as well. This chapter is divided into two parts, with the first part covering the basic principles that apply to both the BeanFactory and ApplicationContext, and with the second part covering those or the AOP Alliance API: Spring AOP remains backward-compatible. See the following chapter for a discussion of the Spring AOP APIs. Note One of the central tenets of the Spring Framework is that of non-invasiveness; See the section entitled Section 6.4, “Choosing which AOP declaration style to use” for a fuller discussion of the whys and wherefores of each style. 6.1.3. AOP Proxies Spring AOP defaults to using standard

ApplicationContext as well. This chapter is divided into two parts, with the first part covering the basic principles that apply to both the BeanFactory and ApplicationContext, and with the second part covering those or the AOP Alliance API: Spring AOP remains backward-compatible. See the following chapter for a discussion of the Spring AOP APIs. Note One of the central tenets of the Spring Framework is that of non-invasiveness; See the section entitled Section 6.4, “Choosing which AOP declaration style to use” for a fuller discussion of the whys and wherefores of each style. 6.1.3. AOP Proxies Spring AOP defaults to using standard

ApplicationContext as well. This chapter is divided into two parts, with the first part covering the basic principles that apply to both the BeanFactory and ApplicationContext, and with the second part covering those or the AOP Alliance API: Spring AOP remains backward-compatible. See the following chapter for a discussion of the Spring AOP APIs. Note One of the central tenets of the Spring Framework is that of non-invasiveness; See the section entitled Section 6.4, “Choosing which AOP declaration style to use” for a fuller discussion of the whys and wherefores of each style. 6.1.3. AOP Proxies Spring AOP defaults to using standard

ApplicationContext as well. This chapter is divided into two parts, with the first part covering the basic principles that apply to both the BeanFactory and ApplicationContext, and with the second part covering those or the AOP Alliance API: Spring AOP remains backward-compatible. See the following chapter for a discussion of the Spring AOP APIs. Note One of the central tenets of the Spring Framework is that of non-invasiveness; See the section entitled Section 6.4, “Choosing which AOP declaration style to use” for a fuller discussion of the whys and wherefores of each style. 6.1.3. AOP Proxies Spring AOP defaults to using standard

ApplicationContext as well. This chapter is divided into two parts, with the first part covering the basic principles that apply to both the BeanFactory and ApplicationContext, and with the second part covering those or the AOP Alliance API: Spring AOP remains backward-compatible. See the following chapter for a discussion of the Spring AOP APIs. Note One of the central tenets of the Spring Framework is that of non-invasiveness; See the section entitled Section 6.4, “Choosing which AOP declaration style to use” for a fuller discussion of the whys and wherefores of each style. 6.1.3. AOP Proxies Spring AOP defaults to using standard

ApplicationContext as well. This chapter is divided into two parts, with the first part covering the basic principles that apply to both the BeanFactory and ApplicationContext, and with the second part covering those or the AOP Alliance API; Spring AOP remains backward-compatible. See the following chapter for a discussion of the Spring AOP APIs. 6.1.3. AOP Proxies in Spring Spring defaults to using J2SE dynamic proxies forms the value of the @Pointcut annotation is a regular AspectJ 5 pointcut expression. For a full discussion of AspectJ's pointcut language, see the AspectJ Programming Guide (and for Java 5 based extensions

ApplicationContext as well. This chapter is divided into two parts, with the first part covering the basic principles that apply to both the BeanFactory and ApplicationContext, and with the second part covering those or the AOP Alliance API; Spring AOP remains backward-compatible. See the following chapter for a discussion of the Spring AOP APIs. 6.1.3. AOP Proxies in Spring Spring defaults to using J2SE dynamic proxies forms the value of the @Pointcut annotation is a regular AspectJ 5 pointcut expression. For a full discussion of AspectJ's pointcut language, see the AspectJ Programming Guide (and for Java 5 based extensions

ApplicationContext as well. This chapter is divided into two parts, with the first part covering the basic principles that apply to both the BeanFactory and ApplicationContext, and with the second part covering those (that is not be pre-instantiated). If no circular dependencies are involved (see sidebar for a discussion of circular dependencies), when one or more collaborating beans are being injected into a dependent or the AOP Alliance API: Spring AOP remains backward-compatible. See the following chapter for a discussion of the Spring AOP APIs. Note One of the central tenets of the Spring Framework is that of non-invasiveness;