java项目开发常用配置文件模板

mybatis config文件

 1 <?xml version="1.0" encoding="UTF-8" ?>
 2 <!DOCTYPE configuration
 3         PUBLIC "-//mybatis.org//DTD Config 3.0//EN"
 4         "http://mybatis.org/dtd/mybatis-3-config.dtd">
 5 <configuration>
 6     <properties resource="jdbc.properties" />
 7     <typeAliases>
 8         <package name="" />
 9     </typeAliases>
10     <environments default="development">
11         <environment id="development">
12             <transactionManager type="JDBC"/>
13             <dataSource type="POOLED">
14                 <property name="driver" value="${jdbc.driver}"/>
15                 <property name="url" value="${jdbc.url}"/>
16                 <property name="username" value="${jdbc.username}"/>
17                 <property name="password" value="${jdbc.password}"/>
18             </dataSource>
19         </environment>
20     </environments>
21     <mappers>
22         <package name=""/>
23     </mappers>
24 </configuration>

mybatis mapper

1 <?xml version="1.0" encoding="UTF-8" ?>
2 <!DOCTYPE mapper
3         PUBLIC "-//mybatis.org//DTD Mapper 3.0//EN"
4         "http://mybatis.org/dtd/mybatis-3-mapper.dtd">
5 <mapper namespace="">
6     
7 </mapper>

spring自动注入

 1 <?xml version="1.0" encoding="UTF-8"?>
 2 <beans xmlns="http://www.springframework.org/schema/beans"
 3        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 4        xmlns:context="http://www.springframework.org/schema/context"
 5        xsi:schemaLocation="http://www.springframework.org/schema/beans
 6        https://www.springframework.org/schema/beans/spring-beans.xsd
 7        http://www.springframework.org/schema/context
 8        http://www.springframework.org/schema/context/spring-context.xsd">
 9 
10     <!--准备SpringIOC自动注入-->
11     <!--
12         1.准备环境
13             xmlns:context="http://www.springframework.org/schema/context"
14 
15             http://www.springframework.org/schema/context
16             http://www.springframework.org/schema/context/spring-context.xsd
17 
18         2.开启自动注入
19             <context:annotation-config/>
20 
21     -->
22     <!--开启⾃动化装配(注⼊)-->
23     <context:annotation-config/>
24     <bean id="userDao" class="com.xxx.dao.UserDao"/>
25     <bean id="userService" class="com.xxx.services.UserSevice"/>
26 </beans>

mysql-propertise

jdbc.driver=com.mysql.cj.jdbc.Driver
jdbc.url=jdbc:mysql://127.0.0.1:3306/dbname?serverTimezone=UTC&useSSL=false&characterEncoding=utf-8
jdbc.username=root
jdbc.password=root

 maven settings.xml

  1 <?xml version="1.0" encoding="UTF-8"?>
  2 
  3 <!--
  4 Licensed to the Apache Software Foundation (ASF) under one
  5 or more contributor license agreements.  See the NOTICE file
  6 distributed with this work for additional information
  7 regarding copyright ownership.  The ASF licenses this file
  8 to you under the Apache License, Version 2.0 (the
  9 "License"); you may not use this file except in compliance
 10 with the License.  You may obtain a copy of the License at
 11 
 12     http://www.apache.org/licenses/LICENSE-2.0
 13 
 14 Unless required by applicable law or agreed to in writing,
 15 software distributed under the License is distributed on an
 16 "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
 17 KIND, either express or implied.  See the License for the
 18 specific language governing permissions and limitations
 19 under the License.
 20 -->
 21 
 22 <!--
 23  | This is the configuration file for Maven. It can be specified at two levels:
 24  |
 25  |  1. User Level. This settings.xml file provides configuration for a single user,
 26  |                 and is normally provided in ${user.home}/.m2/settings.xml.
 27  |
 28  |                 NOTE: This location can be overridden with the CLI option:
 29  |
 30  |                 -s /path/to/user/settings.xml
 31  |
 32  |  2. Global Level. This settings.xml file provides configuration for all Maven
 33  |                 users on a machine (assuming they're all using the same Maven
 34  |                 installation). It's normally provided in
 35  |                 ${maven.conf}/settings.xml.
 36  |
 37  |                 NOTE: This location can be overridden with the CLI option:
 38  |
 39  |                 -gs /path/to/global/settings.xml
 40  |
 41  | The sections in this sample file are intended to give you a running start at
 42  | getting the most out of your Maven installation. Where appropriate, the default
 43  | values (values used when the setting is not specified) are provided.
 44  |
 45  |-->
 46 <settings xmlns="http://maven.apache.org/SETTINGS/1.2.0"
 47           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 48           xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.2.0 https://maven.apache.org/xsd/settings-1.2.0.xsd">
 49   <!-- localRepository
 50    | The path to the local repository maven will use to store artifacts.
 51    |
 52    | Default: ${user.home}/.m2/repository
 53   <localRepository>/path/to/local/repo</localRepository>
 54   -->
 55   <localRepository>D:/WorkSpace/jdk/maven/mavenRepository</localRepository>
 56 
 57   <!-- interactiveMode
 58    | This will determine whether maven prompts you when it needs input. If set to false,
 59    | maven will use a sensible default value, perhaps based on some other setting, for
 60    | the parameter in question.
 61    |
 62    | Default: true
 63   <interactiveMode>true</interactiveMode>
 64   -->
 65 
 66   <!-- offline
 67    | Determines whether maven should attempt to connect to the network when executing a build.
 68    | This will have an effect on artifact downloads, artifact deployment, and others.
 69    |
 70    | Default: false
 71   <offline>false</offline>
 72   -->
 73 
 74   <!-- pluginGroups
 75    | This is a list of additional group identifiers that will be searched when resolving plugins by their prefix, i.e.
 76    | when invoking a command line like "mvn prefix:goal". Maven will automatically add the group identifiers
 77    | "org.apache.maven.plugins" and "org.codehaus.mojo" if these are not already contained in the list.
 78    |-->
 79   <pluginGroups>
 80     <!-- pluginGroup
 81      | Specifies a further group identifier to use for plugin lookup.
 82     <pluginGroup>com.your.plugins</pluginGroup>
 83     -->
 84   </pluginGroups>
 85 
 86   <!-- TODO Since when can proxies be selected as depicted? -->
 87   <!-- proxies
 88    | This is a list of proxies which can be used on this machine to connect to the network.
 89    | Unless otherwise specified (by system property or command-line switch), the first proxy
 90    | specification in this list marked as active will be used.
 91    |-->
 92   <proxies>
 93     <!-- proxy
 94      | Specification for one proxy, to be used in connecting to the network.
 95      |
 96     <proxy>
 97       <id>optional</id>
 98       <active>true</active>
 99       <protocol>http</protocol>
100       <username>proxyuser</username>
101       <password>proxypass</password>
102       <host>proxy.host.net</host>
103       <port>80</port>
104       <nonProxyHosts>local.net|some.host.com</nonProxyHosts>
105     </proxy>
106     -->
107   </proxies>
108 
109   <!-- servers
110    | This is a list of authentication profiles, keyed by the server-id used within the system.
111    | Authentication profiles can be used whenever maven must make a connection to a remote server.
112    |-->
113   <servers>
114     <!-- server
115      | Specifies the authentication information to use when connecting to a particular server, identified by
116      | a unique name within the system (referred to by the 'id' attribute below).
117      |
118      | NOTE: You should either specify username/password OR privateKey/passphrase, since these pairings are
119      |       used together.
120      |
121     <server>
122       <id>deploymentRepo</id>
123       <username>repouser</username>
124       <password>repopwd</password>
125     </server>
126     -->
127 
128     <!-- Another sample, using keys to authenticate.
129     <server>
130       <id>siteServer</id>
131       <privateKey>/path/to/private/key</privateKey>
132       <passphrase>optional; leave empty if not used.</passphrase>
133     </server>
134     -->
135   </servers>
136 
137   <!-- mirrors
138    | This is a list of mirrors to be used in downloading artifacts from remote repositories.
139    |
140    | It works like this: a POM may declare a repository to use in resolving certain artifacts.
141    | However, this repository may have problems with heavy traffic at times, so people have mirrored
142    | it to several places.
143    |
144    | That repository definition will have a unique id, so we can create a mirror reference for that
145    | repository, to be used as an alternate download site. The mirror site will be the preferred
146    | server for that repository.
147    |-->
148   <mirrors>
149     <!-- mirror
150      | Specifies a repository mirror site to use instead of a given repository. The repository that
151      | this mirror serves has an ID that matches the mirrorOf element of this mirror. IDs are used
152      | for inheritance and direct lookup purposes, and must be unique across the set of mirrors.
153      |
154     <mirror>
155       <id>mirrorId</id>
156       <mirrorOf>repositoryId</mirrorOf>
157       <name>Human Readable Name for this Mirror.</name>
158       <url>http://my.repository.com/repo/path</url>
159     </mirror>
160      -->
161      <mirror>
162      <id>aliyunmaven</id>
163      <mirrorOf>central</mirrorOf>
164      <name>阿里云公共仓库</name>
165      <url>https://maven.aliyun.com/repository/central</url>
166     </mirror>
167     <mirror>
168       <id>repo1</id>
169       <mirrorOf>central</mirrorOf>
170       <name>central repo</name>
171       <url>http://repo1.maven.org/maven2/</url>
172     </mirror>
173     <mirror>
174      <id>aliyunmaven</id>
175      <mirrorOf>apache snapshots</mirrorOf>
176      <name>阿里云阿帕奇仓库</name>
177      <url>https://maven.aliyun.com/repository/apache-snapshots</url>
178     </mirror>
179   </mirrors>
180 
181   <!-- profiles
182    | This is a list of profiles which can be activated in a variety of ways, and which can modify
183    | the build process. Profiles provided in the settings.xml are intended to provide local machine-
184    | specific paths and repository locations which allow the build to work in the local environment.
185    |
186    | For example, if you have an integration testing plugin - like cactus - that needs to know where
187    | your Tomcat instance is installed, you can provide a variable here such that the variable is
188    | dereferenced during the build process to configure the cactus plugin.
189    |
190    | As noted above, profiles can be activated in a variety of ways. One way - the activeProfiles
191    | section of this document (settings.xml) - will be discussed later. Another way essentially
192    | relies on the detection of a property, either matching a particular value for the property,
193    | or merely testing its existence. Profiles can also be activated by JDK version prefix, where a
194    | value of '1.4' might activate a profile when the build is executed on a JDK version of '1.4.2_07'.
195    | Finally, the list of active profiles can be specified directly from the command line.
196    |
197    | NOTE: For profiles defined in the settings.xml, you are restricted to specifying only artifact
198    |       repositories, plugin repositories, and free-form properties to be used as configuration
199    |       variables for plugins in the POM.
200    |
201    |-->
202   <profiles>
203     <!-- profile
204      | Specifies a set of introductions to the build process, to be activated using one or more of the
205      | mechanisms described above. For inheritance purposes, and to activate profiles via <activatedProfiles/>
206      | or the command line, profiles have to have an ID that is unique.
207      |
208      | An encouraged best practice for profile identification is to use a consistent naming convention
209      | for profiles, such as 'env-dev', 'env-test', 'env-production', 'user-jdcasey', 'user-brett', etc.
210      | This will make it more intuitive to understand what the set of introduced profiles is attempting
211      | to accomplish, particularly when you only have a list of profile id's for debug.
212      |
213      | This profile example uses the JDK version to trigger activation, and provides a JDK-specific repo.
214     <profile>
215       <id>jdk-1.4</id>
216 
217       <activation>
218         <jdk>1.4</jdk>
219       </activation>
220 
221       <repositories>
222         <repository>
223           <id>jdk14</id>
224           <name>Repository for JDK 1.4 builds</name>
225           <url>http://www.myhost.com/maven/jdk14</url>
226           <layout>default</layout>
227           <snapshotPolicy>always</snapshotPolicy>
228         </repository>
229       </repositories>
230     </profile>
231     -->
232 
233     <!--
234      | Here is another profile, activated by the property 'target-env' with a value of 'dev', which
235      | provides a specific path to the Tomcat instance. To use this, your plugin configuration might
236      | hypothetically look like:
237      |
238      | ...
239      | <plugin>
240      |   <groupId>org.myco.myplugins</groupId>
241      |   <artifactId>myplugin</artifactId>
242      |
243      |   <configuration>
244      |     <tomcatLocation>${tomcatPath}</tomcatLocation>
245      |   </configuration>
246      | </plugin>
247      | ...
248      |
249      | NOTE: If you just wanted to inject this configuration whenever someone set 'target-env' to
250      |       anything, you could just leave off the <value/> inside the activation-property.
251      |
252     <profile>
253       <id>env-dev</id>
254 
255       <activation>
256         <property>
257           <name>target-env</name>
258           <value>dev</value>
259         </property>
260       </activation>
261 
262       <properties>
263         <tomcatPath>/path/to/tomcat/instance</tomcatPath>
264       </properties>
265     </profile>
266     -->
267     <profile>  
268         <repositories>
269            <repository>
270                 <id>aliyunmaven</id>
271                 <name>aliyunmaven</name>
272                 <url>https://maven.aliyun.com/repository/public</url>
273                 <layout>default</layout>
274                 <releases>
275                         <enabled>true</enabled>
276                 </releases>
277                 <snapshots>
278                         <enabled>true</enabled>
279                 </snapshots>
280             </repository>
281             <repository>
282                 <id>MavenCentral</id>
283                 <url>http://repo1.maven.org/maven2/</url>
284             </repository>
285             <repository>
286                 <id>aliyunmavenApache</id>
287                 <url>https://maven.aliyun.com/repository/apache-snapshots</url>
288             </repository>
289         </repositories>             
290      </profile>
291   </profiles>
292 
293   <!-- activeProfiles
294    | List of profiles that are active for all builds.
295    |
296   <activeProfiles>
297     <activeProfile>alwaysActiveProfile</activeProfile>
298     <activeProfile>anotherAlwaysActiveProfile</activeProfile>
299   </activeProfiles>
300   -->
301 </settings>

 spring aop

 1 <?xml version="1.0" encoding="UTF-8"?>
 2 <beans xmlns="http://www.springframework.org/schema/beans"
 3        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 4        xmlns:context="http://www.springframework.org/schema/context"
 5        xmlns:aop="http://www.springframework.org/schema/aop"
 6        xsi:schemaLocation="http://www.springframework.org/schema/beans
 7        https://www.springframework.org/schema/beans/spring-beans.xsd
 8        http://www.springframework.org/schema/context
 9        http://www.springframework.org/schema/context/spring-context.xsd
10        http://www.springframework.org/schema/aop
11        http://www.springframework.org/schema/aop/spring-aop.xsd
12 ">
13     <context:component-scan base-package="com.xxx.services"/>
14 </beans>

 如果spring aop注解没有生效(没有增强效果),可以试试下面的配置:

 1 <?xml version="1.0" encoding="UTF-8"?>
 2 <beans xmlns="http://www.springframework.org/schema/beans"
 3        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 4        xmlns:context="http://www.springframework.org/schema/context"
 5        xmlns:aop="http://www.springframework.org/schema/aop"
 6        xsi:schemaLocation="http://www.springframework.org/schema/beans
 7        https://www.springframework.org/schema/beans/spring-beans.xsd
 8        http://www.springframework.org/schema/context
 9        http://www.springframework.org/schema/context/spring-context.xsd
10        http://www.springframework.org/schema/aop
11        http://www.springframework.org/schema/aop/spring-aop.xsd
12 ">
13     <context:component-scan base-package="com.xxx"/>
14     <!--如果使用注解进行切面,如果AOP增强不生效,可以试试加上下面的配置-->
15     <aop:aspectj-autoproxy expose-proxy="true" proxy-target-class="true"/>
16 
17 </beans>

 如果想使用xml的方式实现AOP,配置文件可以这样子写:

 1 <aop:config>
 2         <aop:aspect ref="logCut" id="logCut">
 3             <aop:pointcut id="cut" expression="execution(* com.xxx.services..*.*(..))"/>
 4             <aop:before method="before" pointcut-ref="cut"/>
 5             <aop:after method="after" pointcut-ref="cut"/>
 6             <aop:after-returning method="afterReturn" pointcut-ref="cut"/>
 7             <aop:after-throwing method="throwException" pointcut-ref="cut" throwing="e"/>
 8             <aop:around method="aroundAfter" pointcut-ref="cut"/>
 9         </aop:aspect>
10     </aop:config>

实现AOP的类只需要加上@Component注解即可。

posted on 2023-09-25 16:13  ymworkroom  阅读(48)  评论(0编辑  收藏  举报