Spring Property Injection Concepts: Difference between revisions
Jump to navigation
Jump to search
| Line 2: | Line 2: | ||
* [[Spring_Framework#Spring_Framework_Core_Technologies_Concepts|Spring Framework]] | * [[Spring_Framework#Spring_Framework_Core_Technologies_Concepts|Spring Framework]] | ||
=Overview= | |||
Spring has two different, but related kinds of configurations: '''bean wiring''', which refers to declaring application components and their dependencies, and how those dependencies should be injected into each other, as described in the [[Spring_Dependency_Injection_and_Inversion_of_Control_Container_Concepts|Dependency Injection and Inversion of Control Container]] section, and '''property injection''', which is the process that allows external pieces of data, known as [[#Configuration_Property|configuration properties]], to be provided to the application runtime at startup or while it is running, in form of Java system properties, environment variables and by other means. This section addresses property injection concepts. | |||
=The Environment Abstraction= | =The Environment Abstraction= | ||
Revision as of 05:25, 2 December 2018
Internal
Overview
Spring has two different, but related kinds of configurations: bean wiring, which refers to declaring application components and their dependencies, and how those dependencies should be injected into each other, as described in the Dependency Injection and Inversion of Control Container section, and property injection, which is the process that allows external pieces of data, known as configuration properties, to be provided to the application runtime at startup or while it is running, in form of Java system properties, environment variables and by other means. This section addresses property injection concepts.