dubbo的启动方法

Dubbo服务的运行方式：

1、使用Servlet容器运行（Tomcat、Jetty等）----不可取 缺点：增加复杂性（端口、管理） 浪费资源（内存）
2、自建Main方法类来运行（spring容器） ----不建议（本地调试可用） 缺点： Dobbo本身提供的高级特性没用上 自已编写启动类可能会有缺陷
3、使用Dubbo框架提供的Main方法类来运行（Spring容器）----建议使用 优点：框架本身提供（com.alibaba.dubbo.Container.Main） 可实现优雅关机（ShutdownHook）
注意点： spring-context.xml <import resource="classpath:spring/spring-xxx.xml" />

一、服务的启动方式：servelet容器过于庞大，占用资源。
二、main方法在本地用的比较普遍，本地开发调试，单元测试，要掌握，不建议生产使用。
三、dubbo提供的启动类：建议使用dubbo服务自带的启动类，好处是优雅关机，避免强行关闭导致数据丢失。

以下是dubbo服务的打包及启动配置，打出jar包的服务：

1. <build>
2. <finalName>edu-service-user</finalName>
3. <resources>
4. <resource>
5. <targetPath>${project.build.directory}/classes</targetPath>
6. <directory>src/main/resources</directory>
7. <filtering>true</filtering>
8. <includes>
9. <include>**/*.xml</include>
10. <include>**/*.properties</include>
11. </includes>
12. </resource>
13. <!-- 结合com.alibaba.dubbo.container.Main -->
14. <resource>
15. <targetPath>${project.build.directory}/classes/META-INF/spring</targetPath>
16. <directory>src/main/resources/spring</directory>
17. <filtering>true</filtering>
18. <includes>
19. <include>spring-context.xml</include>
20. </includes>
21. </resource>
22. </resources>
23. <pluginManagement>
24. <plugins>
25. <!-- 解决Maven插件在Eclipse内执行了一系列的生命周期引起冲突 -->
26. <plugin>
27. <groupId>org.eclipse.m2e</groupId>
28. <artifactId>lifecycle-mapping</artifactId>
29. <version>1.0.0</version>
30. <configuration>
31. <lifecycleMappingMetadata>
32. <pluginExecutions>
33. <pluginExecution>
34. <pluginExecutionFilter>
35. <groupId>org.apache.maven.plugins</groupId>
36. <artifactId>maven-dependency-plugin</artifactId>
37. <versionRange>[2.0,)</versionRange>
38. <goals>
39. <goal>copy-dependencies</goal>
40. </goals>
41. </pluginExecutionFilter>
42. <action>
43. <ignore />
44. </action>
45. </pluginExecution>
46. </pluginExecutions>
47. </lifecycleMappingMetadata>
48. </configuration>
49. </plugin>
50. </plugins>
51. </pluginManagement>
52. <plugins>
53. <!-- 打包jar文件时，配置manifest文件，加入lib包的jar依赖 -->
54. <plugin>
55. <groupId>org.apache.maven.plugins</groupId>
56. <artifactId>maven-jar-plugin</artifactId>
57. <configuration>
58. <classesDirectory>target/classes/</classesDirectory>
59. <archive>
60. <manifest>
61. <mainClass>com.alibaba.dubbo.container.Main</mainClass>
62. <!-- 打包时 MANIFEST.MF文件不记录的时间戳版本 -->
63. <useUniqueVersions>false</useUniqueVersions>
64. <addClasspath>true</addClasspath>
65. <classpathPrefix>lib/</classpathPrefix>
66. </manifest>
67. <manifestEntries>
68. <Class-Path>.</Class-Path>
69. </manifestEntries>
70. </archive>
71. </configuration>
72. </plugin>
73. <plugin>
74. <groupId>org.apache.maven.plugins</groupId>
75. <artifactId>maven-dependency-plugin</artifactId>
76. <executions>
77. <execution>
78. <id>copy-dependencies</id>
79. <phase>package</phase>
80. <goals>
81. <goal>copy-dependencies</goal>
82. </goals>
83. <configuration>
84. <type>jar</type>
85. <includeTypes>jar</includeTypes>
86. <useUniqueVersions>false</useUniqueVersions>
87. <outputDirectory>
88. ${project.build.directory}/lib
89. </outputDirectory>
90. </configuration>
91. </execution>
92. </executions>
93. </plugin>
94. </plugins>
95. </build>

五、启动jar包，定位到相应的目录下，执行  java -jar edu-service-user.jar &

修改spring-context.xml文件中对另外两个文件的引用路径：前面加上classpath:spring/spring-mybatis.xml

六、当然了，我们的服务是war包，直接部署在tomcat就ok了。配置如下：

1. <build>
2. <finalName>****-service</finalName>
3. <resources>
4. <resource>
5. <targetPath>${project.build.directory}/classes</targetPath>
6. <directory>src/main/resources</directory>
7. <filtering>true</filtering>
8. <includes>
9. <include>**/*</include>
10. </includes>
11. </resource>
12. <!-- 结合com.alibaba.dubbo.container.Main -->
13. <resource>
14. <targetPath>${project.build.directory}/classes/META-INF/spring</targetPath>
15. <directory>src/main/resources/spring</directory>
16. <filtering>true</filtering>
17. <includes>
18. <include>spring.xml</include>
19. </includes>
20. </resource>
21. </resources>
22. <pluginManagement>
23. <plugins>
24. <!-- 解决Maven插件在Eclipse内执行了一系列的生命周期引起冲突 -->
25. <plugin>
26. <groupId>org.eclipse.m2e</groupId>
27. <artifactId>lifecycle-mapping</artifactId>
28. <version>1.0.0</version>
29. <configuration>
30. <lifecycleMappingMetadata>
31. <pluginExecutions>
32. <pluginExecution>
33. <pluginExecutionFilter>
34. <groupId>org.apache.maven.plugins</groupId>
35. <artifactId>maven-dependency-plugin</artifactId>
36. <versionRange>[2.0,)</versionRange>
37. <goals>
38. <goal>copy-dependencies</goal>
39. </goals>
40. </pluginExecutionFilter>
41. <action>
42. <ignore />
43. </action>
44. </pluginExecution>
45. </pluginExecutions>
46. </lifecycleMappingMetadata>
47. </configuration>
48. </plugin>
49. </plugins>
50. </pluginManagement>
51. <plugins>
52. <plugin>
53. <groupId>org.apache.maven.plugins</groupId>
54. <artifactId>maven-compiler-plugin</artifactId>
55. <version>3.1</version>
56. <configuration>
57. <source>1.8</source>
58. <target>1.8</target>
59. <encoding>UTF-8</encoding>
60. <compilerArgs>
61. <arg>-extdirs</arg>
62. <arg>${project.basedir}/src/main/webapp/WEB-INF/lib</arg>
63. </compilerArgs>
64. </configuration>
65. </plugin>
66. <plugin>
67. <groupId>org.apache.maven.plugins</groupId>
68. <artifactId>maven-war-plugin</artifactId>
69. <version>2.6</version>
70. <configuration>
71. <warName>****</warName>
72. <archive>
73. <addMavenDescriptor>false</addMavenDescriptor>
74. </archive>
75. </configuration>
76. </plugin>
77. </plugins>
78. </build>