attribute defines the type of the bean and uses the fully qualified classname.The value of the id attribute refers to collaborating objects.For example, in a web application scenario, a simple eight (or so) lines of boilerplate web descriptor XML in the file of the application will typically suffice (see Convenient Application Context instantiation for web applications).If you are using the Spring Tool Suite Eclipse-powered development environment this boilerplate configuration can be easily created with few mouse clicks or keystrokes. Typically one does not configure fine-grained domain objects in the container, because it is usually the responsibility of DAOs and business logic to create and load domain objects.However, you can use Spring’s integration with Aspect J to configure objects that have been created outside the control of an Io C container.See Using Aspect J to dependency-inject domain objects with Spring.This is commonly the case in large systems where configuration is split amongst each subsystem, each subsystem having its own set of object definitions.
You can always use fully qualified resource locations instead of relative paths: for example, "file: C:/config/services.xml" or "classpath:/config/services.xml".
Examples of such names would be (without quotes) With component scanning in the classpath, Spring generates bean names for unnamed components, following the rules above: essentially, taking the simple class name and turning its initial character to lower-case.
However, in the (unusual) special case when there is more than one character and both the first and second characters are upper case, the original casing gets preserved. These names can be equivalent aliases to the same bean, and are useful for some situations, such as allowing each component in an application to refer to a common dependency by using a bean name that is specific to that component itself.
It allows you to express the objects that compose your application and the rich interdependencies between such objects. While XML has been the traditional format for defining configuration metadata you can instruct the container to use Java annotations or code as the metadata format by providing a small amount of XML configuration to declaratively enable support for these additional metadata formats.
In most application scenarios, explicit user code is not required to instantiate one or more instances of a Spring Io C container.