Spring 项目的创建与 Bean对象的使用

目录

一.创建Spring项目

1.配置Maven国内源

        如果没有settings.xml文件

        如果已存在settings.xml文件

        删除本地所有的jar包,重新下载

2.引入Spring依赖

3.创建启动类

二.将Bean对象存储到Spring(IoC容器)

1.创建bean对象

2.将bean对象存储到Spring中

        添加Spring配置文件

        注入bean对象

3.读取bean对象

        通过ApplicationContext方式

        通过BeanFactory方式

        两种方式的区别

        getBean()的更多用法

---

一.创建Spring项目

1.配置Maven国内源

如果没有 .m2 文件夹,则自己创建一个 .m2文件夹即可

如果没有settings.xml文件

可以看到我的目录里没有settings.xml文件

创建一个settings.xml文件,然后将以下代码粘贴进去即可

<?xml version="1.0" encoding="UTF-8"?>

<!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you 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 athttp://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. -->

<!--| This is the configuration file for Maven. It can be specified at two levels:|| 1. User Level. This settings.xml file provides configuration for a single user,| and is normally provided in ${user.home}/.m2/settings.xml.|| NOTE: This location can be overridden with the CLI option:|| -s /path/to/user/settings.xml|| 2. Global Level. This settings.xml file provides configuration for all Maven| users on a machine (assuming they're all using the same Maven| installation). It's normally provided in| ${maven.conf}/settings.xml.|| NOTE: This location can be overridden with the CLI option:|| -gs /path/to/global/settings.xml|| The sections in this sample file are intended to give you a running start at| getting the most out of your Maven installation. Where appropriate, the default| values (values used when the setting is not specified) are provided.||-->

-<settings xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://maven.apache.org/SETTINGS/1.0.0">

<!-- localRepository| The path to the local repository maven will use to store artifacts.|| Default: ${user.home}/.m2/repository<localRepository>/path/to/local/repo</localRepository> -->


<!-- interactiveMode| This will determine whether maven prompts you when it needs input. If set to false,| maven will use a sensible default value, perhaps based on some other setting, for| the parameter in question.|| Default: true<interactiveMode>true</interactiveMode> -->


<!-- offline| Determines whether maven should attempt to connect to the network when executing a build.| This will have an effect on artifact downloads, artifact deployment, and others.|| Default: false<offline>false</offline> -->


<!-- pluginGroups| This is a list of additional group identifiers that will be searched when resolving plugins by their prefix, i.e.| when invoking a command line like "mvn prefix:goal". Maven will automatically add the group identifiers| "org.apache.maven.plugins" and "org.codehaus.mojo" if these are not already contained in the list.|-->



-<pluginGroups>

<!-- pluginGroup| Specifies a further group identifier to use for plugin lookup.<pluginGroup>com.your.plugins</pluginGroup> -->


</pluginGroups>

<!-- proxies| This is a list of proxies which can be used on this machine to connect to the network.| Unless otherwise specified (by system property or command-line switch), the first proxy| specification in this list marked as active will be used.|-->



-<proxies>

<!-- proxy| Specification for one proxy, to be used in connecting to the network.|<proxy><id>optional</id><active>true</active><protocol>http</protocol><username>proxyuser</username><password>proxypass</password><host>proxy.host.net</host><port>80</port><nonProxyHosts>local.net|some.host.com</nonProxyHosts></proxy> -->


</proxies>

<!-- servers| This is a list of authentication profiles, keyed by the server-id used within the system.| Authentication profiles can be used whenever maven must make a connection to a remote server.|-->



-<servers>

<!-- server| Specifies the authentication information to use when connecting to a particular server, identified by| a unique name within the system (referred to by the 'id' attribute below).|| NOTE: You should either specify username/password OR privateKey/passphrase, since these pairings are| used together.|<server><id>deploymentRepo</id><username>repouser</username><password>repopwd</password></server> -->


<!-- Another sample, using keys to authenticate.<server><id>siteServer</id><privateKey>/path/to/private/key</privateKey><passphrase>optional; leave empty if not used.</passphrase></server> -->


</servers>

<!-- mirrors| This is a list of mirrors to be used in downloading artifacts from remote repositories.|| It works like this: a POM may declare a repository to use in resolving certain artifacts.| However, this repository may have problems with heavy traffic at times, so people have mirrored| it to several places.|| That repository definition will have a unique id, so we can create a mirror reference for that| repository, to be used as an alternate download site. The mirror site will be the preferred| server for that repository.|-->



-<mirrors>


-<mirror>

<id>alimaven</id>

<name>aliyun maven</name>

<url>http://maven.aliyun.com/nexus/content/groups/public/</url>

<mirrorOf>central</mirrorOf>

</mirror>

<!-- mirror| Specifies a repository mirror site to use instead of a given repository. The repository that| this mirror serves has an ID that matches the mirrorOf element of this mirror. IDs are used| for inheritance and direct lookup purposes, and must be unique across the set of mirrors.|<mirror><id>mirrorId</id><mirrorOf>repositoryId</mirrorOf><name>Human Readable Name for this Mirror.</name><url>http://my.repository.com/repo/path</url></mirror> -->


</mirrors>

<!-- profiles| This is a list of profiles which can be activated in a variety of ways, and which can modify| the build process. Profiles provided in the settings.xml are intended to provide local machine- | specific paths and repository locations which allow the build to work in the local environment.|| For example, if you have an integration testing plugin - like cactus - that needs to know where| your Tomcat instance is installed, you can provide a variable here such that the variable is| dereferenced during the build process to configure the cactus plugin.|| As noted above, profiles can be activated in a variety of ways. One way - the activeProfiles| section of this document (settings.xml) - will be discussed later. Another way essentially| relies on the detection of a system property, either matching a particular value for the property,| or merely testing its existence. Profiles can also be activated by JDK version prefix, where a| value of '1.4' might activate a profile when the build is executed on a JDK version of '1.4.2_07'.| Finally, the list of active profiles can be specified directly from the command line.|| NOTE: For profiles defined in the settings.xml, you are restricted to specifying only artifact| repositories, plugin repositories, and free-form properties to be used as configuration| variables for plugins in the POM.||-->



-<profiles>

<!-- profile| Specifies a set of introductions to the build process, to be activated using one or more of the| mechanisms described above. For inheritance purposes, and to activate profiles via <activatedProfiles/>| or the command line, profiles have to have an ID that is unique.|| An encouraged best practice for profile identification is to use a consistent naming convention| for profiles, such as 'env-dev', 'env-test', 'env-production', 'user-jdcasey', 'user-brett', etc.| This will make it more intuitive to understand what the set of introduced profiles is attempting| to accomplish, particularly when you only have a list of profile id's for debug.|| This profile example uses the JDK version to trigger activation, and provides a JDK-specific repo.<profile><id>jdk-1.4</id><activation><jdk>1.4</jdk></activation><repositories><repository><id>jdk14</id><name>Repository for JDK 1.4 builds</name><url>http://www.myhost.com/maven/jdk14</url><layout>default</layout><snapshotPolicy>always</snapshotPolicy></repository></repositories></profile> -->


<!--| Here is another profile, activated by the system property 'target-env' with a value of 'dev',| which provides a specific path to the Tomcat instance. To use this, your plugin configuration| might hypothetically look like:|| ...| <plugin>| <groupId>org.myco.myplugins</groupId>| <artifactId>myplugin</artifactId>|| <configuration>| <tomcatLocation>${tomcatPath}</tomcatLocation>| </configuration>| </plugin>| ...|| NOTE: If you just wanted to inject this configuration whenever someone set 'target-env' to| anything, you could just leave off the <value/> inside the activation-property.|<profile><id>env-dev</id><activation><property><name>target-env</name><value>dev</value></property></activation><properties><tomcatPath>/path/to/tomcat/instance</tomcatPath></properties></profile> -->


</profiles>

<!-- activeProfiles| List of profiles that are active for all builds.|<activeProfiles><activeProfile>alwaysActiveProfile</activeProfile><activeProfile>anotherAlwaysActiveProfile</activeProfile></activeProfiles> -->


</settings>

如果已存在settings.xml文件

则右键这个xml文件,用idea打开,然后找到<mirrors><mirrors>将红框的内容粘贴进去即可

<mirror>
        <id>alimaven</id>
        <name>aliyun maven</name>
        <url>http://maven.aliyun.com/nexus/content/groups/public/</url>
        <mirrorOf>central</mirrorOf>        
      </mirror>

此时就完成了Maven国内源的配置

删除本地所有的jar包,重新下载

本地仓库地址:

全部删除

然后再回到idea 的 pom.xml文件里刷新Maven

下载成功后,即可完成

2.引入Spring依赖

在Maven项目里添加Spring框架的支持,在pom.xml文件里添加以下代码:

<dependencies>
   <dependency>
        <groupId>org.springframework</groupId>
        <artifactId>spring-context</artifactId>
        <version>5.2.3.RELEASE</version>
    </dependency>
  
    <dependency>
        <groupId>org.springframework</groupId>
        <artifactId>spring-beans</artifactId>
        <version>5.2.3.RELEASE</version>
    </dependency>
</dependencies>

粘贴后,刷新Maven即可完成下载,由此,Maven项目变成了Spring项目

3.创建启动类

java目录里创建个启动类即可

二.将Bean对象存储到Spring(IoC容器)

1.创建bean对象

如图,我们创建了一个学生对象

2.将bean对象存储到Spring中

添加Spring配置文件

在resources里创建spring-config.xml文件,然后粘贴以下代码

<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans"
       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       xmlns:content="http://www.springframework.org/schema/context"
       xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd http://www.springframework.org/schema/context https://www.springframework.org/schema/context/spring-context.xsd">
        
</beans>

注入bean对象

bean是通过Spring配置文件注入到Spring的

        <bean id="Student" class="Spring.demo.Student"></bean>

此时,这个bean对象其实并没有真正存入Spring容器中,目前只是设置了,并没有执行

只有到调用了相关的方法后才会真正存入容器里, 类似于单例模式里的懒汉模式

3.读取bean对象

通过ApplicationContext方式

得到Spring上下文对象

ApplicationContext context = new ClassPathXmlApplicationContext("spring-config.xml");

通过Spring上下文对象获取指定的bean对象

context.getBean("Student");

使用bean对象

通过BeanFactory方式

唯一不同的是获取spring上下文对象的代码

import Spring.demo.Student;
import org.springframework.beans.factory.BeanFactory;
import org.springframework.beans.factory.xml.XmlBeanFactory;
import org.springframework.core.io.ClassPathResource;

import javax.annotation.Resource;
import java.security.cert.X509Certificate;

public class App2 {
    public static void main(String[] args) {
        //得到Spring上下文对象
        BeanFactory beanFactory =
                new XmlBeanFactory(new ClassPathResource("spring-config.xml"));
        //得到指定的bean对象
        Student student = (Student) beanFactory.getBean("Student");
        //使用bean对象
        student.sayHello();
    }
}

两种方式的区别

现在计算机内存充足 , BeanFactory方式已经是过时的方式了

相同点:        都是容器管理对象,都可以获取bean对象

不同点:        1.ApplicationContext 是 BeanFactory 的子类, ApplicationContext 拥有更多的功能                            (国际化支持,资源访问支持,事件传播等方面的支持)

                    2.加载bean的机制不同.   BeanFactory是懒加载,按需加载(用到一个bean再加载一个                           bean), ApplicationContext 则是一次性加载所有的 bean对象

                    3.基于第2点,ApplicationContext在启动时很慢,占用的内存大,但启动后获取对象非常

                        快(性能强) ,   BeanFactory启动时很快,占用内存很小(按需加载bean),但后续查询慢.

getBean()的更多用法

用法1:      根据名称获取bean对象

使用这种方法需要对getBean()的返回值 进行 类型强转

Student student = (Student) context.getBean("Student");

用法2:      根据类型获取bean对象

Student student = context.getBean(Student.class);

只适用于容器中每个类型都是独有的情况

如果存在同一个类型注入到spring容器多次 的情况下,使用此方法就会报错: 无法判断要获取哪个bean

如图,我们在Spring配置文件中 , 将Student类型注入两次 , id 分别为 student 和 student2

此时运行就会报错

用法3:      根据 名称+类型 获取bean对象

Student student = context.getBean("Student",Student.class);

推荐使用这种方法,避免了类型强转,使代码看起来更优雅

如图:即使存在两个同样类型bean对象,由于有名称指定唯一的 id,因此不会报错