1.创建Java工程
在工程上，右键- New - Module，如下：
指明Java工程的名称及使用的JDK版本：
创建包；
在包下创建类，即可；
测试代码；
点击运行即可；
2.创建Java Web工程
2.1.IDEA中配置Tomcat
在IDEA中配置Tomcat之前，需要保证已经安装并配置了Tomcat的环境变量。如果没有安装并配置，可以
参考《 尚硅谷_宋红康_Tomcat8.5快速部署.docx 》配置完成以后，在命令行输入：catalina run 。能够
启动tomcat，则证明安装配置成功
下面看如何在IDEA中配置
配置Tomcat Server的位置：
这里配置Tomcat的名称以及配置应用服务器的位置。根据自己Tomcat的安装位置决定。
配置好后，如下图所示：
2.2.创建web工程
选择New Module，指明当前工程的名称：
选中当前创建的工程，添加框架支持：
选择：Web Application，选择Create web.xml，如下：
2.3.配置web 工程并运行
部署当前的web项目：
选择第2项：
可以修改Application context，如下：
配置当前web工程的详细信息，如下
配置好后，可以直接运行：
2.4.乱码的解决
如果Tomcat日志出现乱码，需要配置：
解决方案：
1) 点击Help => Edit custom VM Options，在最后面添加
-Dfile.encoding=UTF-8
2）在当前tomcat实例中配置VM option，添加
-Dfile.encoding=UTF-8
在第二步的Startup/Connection页签的Run和Debug添加一个Key为JAVA_TOOL_OPTIONS，value为Dfile.encoding=UTF-8的环境变变量
3）保存后重启IDEA，可发现控制台中文乱码显示正常了
3.创建Maven Java工程
3.1.Maven的介绍
Maven是一款自动化构建工具，专注服务于Java平台的项目构建和依赖管理 。在JavaEE开发的历史上构
建工具的发展也经历了一系列的演化和变迁：
构建环节：
3.2.Maven的配置
maven的下载 – 解压 – 环境变量的配置这里就不赘述了，需要的参考03-资料\05-Maven的配置中的《 尚
硅谷_Maven的配置_V2.0.docx 》。下面直接整合Maven。选择自己Maven的目录，和settings文件，然后
配置自己的仓库reposiroty。
3.3.Maven 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 at http://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 xmlns="http://maven.apache.org/SETTINGS/1.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd"> <localRepository>D:\dev_tools\Java\maven\repmaven</localRepository> <!-- 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 | 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> --> <mirror> <id>nexus-aliyun</id> <mirrorOf>central</mirrorOf> <name>Nexus aliyun</name> <url>http://maven.aliyun.com/nexus/content/groups/public</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> --> <profile> <id>jdk-1.8</id> <activation> <activeByDefault>true</activeByDefault> <jdk>1.8</jdk> </activation> <properties> <maven.compiler.source>1.8</maven.compiler.source> <maven.compiler.target>1.8</maven.compiler.target> <maven.compiler.compilerVersion>1.8</maven.compiler.compilerVersion> </properties> </profile> </profiles> <!-- activeProfiles | List of profiles that are active for all builds. | <activeProfiles> <activeProfile>alwaysActiveProfile</activeProfile> <activeProfile>anotherAlwaysActiveProfile</activeProfile> </activeProfiles> --> </settings>
3.3.Maven Java工程的创建
指明当前maven工程的名称、模板等信息。这里要求一个项目组的jdk版本必须一致。
通过坐标，就可以定位仓库中具体的jar包。如下：
新创建的maven 的java工程缺少相应的resources文件目录，需要创建如下：
指明main下resources的文件目录类型：
类似的操作test目录下，提供resources即可。
这里说明Maven的java工程的目录结构：
- main目录用于存放主程序
- test目录用于存放测试程序
- java目录用于存放源代码文件
- resources目录用于存放配置和资源文件
Maven仓库配置注意：
3.4.编写代码及测试
第1步：创建Maven的核心配置文件pom.xml
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> <modelVersion>4.0.0</modelVersion> <groupId>test2.maven</groupId> <artifactId>test2</artifactId> <version>1.0-SNAPSHOT</version> <name>test2</name> <dependencies> <!--添加test依赖--> <dependency> <groupId>junit</groupId> <artifactId>junit</artifactId> <version>4.13.2</version> //这里版本注意一下 <scope>test</scope> </dependency> </dependencies> </project>
第2步：编写主程序代码
在src/main/java/test_maven2目录下新建文件HelloMaven.java
package test_maven; /** * ClassName: HelloMaven * Package: test_maven * Description: * * @Author 栗家龙 * @Create 2023/9/28 9:07 * @Version 1.0 */ public class HelloMaven { public String hello(String message){ return message; } }
第三步：编写测试代码
在src/test/java/test2_maven目录下新建文件HelloMavenTets
package test2_maven; import org.junit.Test; import test_maven.HelloMaven; /** * ClassName: HelloMavenTest * Package: test2_maven * Description: * * @Author 栗家龙 * @Create 2023/9/28 9:09 * @Version 1.0 */ public class HelloMavenTest { @Test public void testHelloMaven(){ HelloMaven helloMaven = new HelloMaven(); System.out.println(helloMaven.hello("Mave 哈哈哈")); } }
第4步：运行几个基本的Maven命令
目录下也会有对应的生命周期。其中常用的是：clean、compile、package、install。
比如这里install，如果其他项目需要将这里的模块作为依赖使用，那就可以install。安装到本地仓库的位
置。
3.5.创建Maven Web工程
指明Maven的web工程的名称和模板。如下：
在Tomcat上进行部署：
配置部署的详细信息：
3.6.开发jsp依赖jar包
1、找不到HttpServlet错误
如果看到JSP报错： The superclass "javax.servlet.http.HttpServlet" was not found on
the Java Build Path 可以加入如下依赖解决。
<dependency> <groupId>javax.servlet</groupId> <artifactId>servlet-api</artifactId> <version>2.5</version> <scope>provided</scope> </dependency>
2、EL表达式没有提示问题
${pageContext}这个EL表达式中通过pageContext对象访问reuqest属性时本身是应该有提示的，但如果没
有的话加入下面依赖即可。
<dependency> <groupId>javax.servlet.jsp</groupId> <artifactId>jsp-api</artifactId> <version>2.1.3-b06</version> <scope>provided</scope> </dependency>
同时，针对index.jsp文件，修改一下文件头信息为:
<%@page language="java" pageEncoding="utf-8" contentType="text/html;UTF-8" %>
4.关键数据库
4.1.关联方式
找到数据库选项：
添加指定数据库：
配置MySQL数据库的详细信息：
表面上很多人认为配置 Database 就是为了有一个 GUI 管理数据库功能，但是这并不是 IntelliJ IDEA 的
Database 最重要特性。数据库的 GUI 工具有很多，IntelliJ IDEA 的 Database 也没有太明显的优势。
IntelliJ IDEA 的 Database 最大特性就是对于 Java Web 项目来讲，常使用的 ORM 框架，如 Hibernate、
Mybatis 有很好的支持，比如配置好了 Database 之后，IntelliJ IDEA 会自动识别 domain 对象与数据表的
关系，也可以通过 Database 的数据表直接生成 domain 对象等。
4.2.常用操作
展示ER图：
可以导出文件：
浙公网安备 33010602011771号