From f43512c3818a868b37f8e2b5fd10f03e7e23cba5 Mon Sep 17 00:00:00 2001 From: Chris Beams Date: Tue, 10 Aug 2010 13:48:26 +0000 Subject: [PATCH] Remove dependency-check coverage from reference docs (SPR-7303) - 'dependency-check' attribute of the element was removed in the spring-beans-3.0 XSD; documentation now reflects this change. - 'autodetect' was removed from the enumeration of possible values for autowire mode in the spring-beans-3.0 XSD; documentation now reflects this change. Note that the underlying functionality for these values has not been removed from Spring Core. Users of Spring 3.0 who still need this support may choose to use spring-beans-2.5.xsd in order to preserve backward-compatibility. git-svn-id: https://src.springframework.org/svn/spring-framework/trunk@3551 50f2f4bb-b051-0410-bef5-90022cba6387 --- spring-framework-reference/src/beans.xml | 97 +----------------------- 1 file changed, 1 insertion(+), 96 deletions(-) diff --git a/spring-framework-reference/src/beans.xml b/spring-framework-reference/src/beans.xml index 9211a8a88ea..67f2e9867bf 100644 --- a/spring-framework-reference/src/beans.xml +++ b/spring-framework-reference/src/beans.xml @@ -481,13 +481,6 @@ List userList service.getUsernameList(); - - dependency checking mode - - - - - lazy-initialization mode @@ -2052,10 +2045,7 @@ support=support@example.co.uk one exists, a fatal exception is thrown, which indicates that you may not use byType autowiring for that bean. If there are no matching beans, nothing happens; the - property is not set. If this is not desirable, setting the - dependency-check="objects" attribute value - specifies that an error should be thrown in this - case. + property is not set. @@ -2067,14 +2057,6 @@ support=support@example.co.uk error is raised. - - autodetect - - Chooses constructor or - byType through introspection of the bean - class. If a default no-arg constructor is found, the - byType mode is applied. - @@ -2203,83 +2185,6 @@ support=support@example.co.uk -
- Checking for dependencies - - - - The Spring IoC container can check for unresolved dependencies of - a bean deployed into the container. When enabling checking for - unresolved dependencies all JavaBean properties of the bean must have - explicit values set for them in the bean definition or have their values - set via autowiring. - - This feature is useful when you want to ensure that all properties - (or all properties of a certain type) are set on a bean. A bean class - often has default values for many properties, or some properties do not - apply to all usage scenarios, so this feature is of limited use. You can - enable dependency checking per bean, just as with the autowiring - functionality. The default is to not check - dependencies. In XML-based configuration metadata, you specify - dependency checking via the dependency-check - attribute in a bean definition, which can have the following - values. - - - Dependency checking modes - - - - - - - - - Mode - - Explanation - - - - - - none - - (Default) No dependency checking. Properties of the - bean that have no value specified for them are not - set. - - - - simple - - Dependency checking for primitive types and - collections (everything except collaborators). - - - - object - - Dependency checking for collaborators - only. - - - - all - - Dependency checking for collaborators, primitive - types, and collections. - - - -
- - If you use Java 5 and thus have access to source-level - annotations, you may find to be of - interest. -
-
Method injection