Shulou(Shulou.com)06/02 Report--

Environment:

1. Environmental preparation

1. Development tools: Eclipse IDE (higher versions recommended)

JDK version: JDK 1.7

3. Project management: Maven3.1.1

2. installation steps

1. Install jdk1.7 and configure environment variables (I believe everyone will do it, here is no longer repeated description)

2. Install maven: maven installation process is the process of decompression (I have helped you decompress, directory: E:\myprj\jeesz-maven\apache-maven-3.1.1), for the convenience of everyone, here has provided the relevant installation package, will be shared in the packaged directory.

3.mavan configuration environment variables, right-click my computer properties advanced system settings environment variables to find (system variable path), in the first input of your maven installation package path, declaration: because the previous step decompressed the specified directory, so the configuration is as follows:

E:\myprj\jeesz-maven\apache-maven-3.1.1\bin;

I believe that everyone has been equipped with environmental variables, if you are not very clear, please query the relevant information to understand the relevant knowledge of maven.

4. Open cmd and type: mvn -version. The following results show that your maven installation is successful.

mvn is a maven command, mvn-version is to view version information, my operating system is 64-bit WIN7, installed maven is 3.1.1, if you can print the above information, indicating that this Maven3 has been installed on your computer.

5. Create workspace (select j2ee view after entering)

6. Configure Eclipse encoding to UTF-8

Select Window> Prefences> General> Workspace from Eclipse toolbar

7. Configure the jre environment (before you need to install jdk version 1.7, here you use the installed jdk to configure):

Select Window « Prefences » java « Installed JREs » Edit « Select Yourself Local Jdk Installation Path » Finished » OK

8. Remove JavaScript validation and other information (because the project uses a lot of js, css, xml and other files in different formats, considering the execution time of each compilation, so some validation information is temporarily removed here)

Window》Prefrences》Validation》Suspend all validators》ok

9. Modify the maven settings.xml configuration file you just installed, the path is as follows: E:\myprj\jeesz-maven\apache-maven-3.1.1\conf,

Add local repository address: E:/myprj/jeesz-maven/apache-maven-3.1.1/repository

Modify the central repository path (under normal network conditions, you can download missing jar packages from the remote central repository, I use Oschina's central repository here, if the network has problems,

You can use your own company's private server to load the relevant jar package). Considering that everyone's package sometimes cannot be downloaded, I also share the jar package needed for the project here, all of which are placed in the following directory:

E:/myprj/jeesz-maven/apache-maven-3.1.1/repository

10. Configuration maven installation directory and local library directory loaded by Setting file in Eclipse

11. Import Maven Project

File Import Existing Maven Projects Next

Select your local maven project (check jeesz-project root directory) and click OK

After loading all the items, click finish to finish

Reminder: This import process takes a while, because I am locally connected to the network, so I will download all the jar packages needed by the project from the remote central repository. Please wait patiently.

If you are using a local library, you don't have to wait long, and if you are using a company private server, the wait time is not very long.

Imported project information

The package for the local library has been downloaded

12. After downloading all jar packages, update maven project:

1)Select all items 2) Right-click maven> Update project Select all> Check associated items> Click ok

If the project also has a red X error, it must be missing the relevant jar package, you can use:

Window> showView> problem Window View exception information

If the jar package is missing, you can copy the jar package we provided directly to your specified directory

After all errors in the project are cleared, the next step can be carried out (as shown in the figure below).

Select all projects to clean up: Project> clean

13. Try compiling and packaging the project to see if there are any problems:

Note: Generally we package compilation for the root project, because it is configured with all dependencies. Right-click jeesz-project《Run As》Maven build

Enter clean install -X command in the pop-up dialog box, check Skip tests, Run…

Reminder: If you are not familiar with the maven command, you can check the relevant information.

Here's a simple explanation: clean install -X means clean up all projects and load the jar wrapper to the local library, where-X means output information (usually-X can be used when maven problems occur to locate problems).

At this point, the console starts compiling and loading all the packages. This process is a bit long. Please wait patiently.

The following results indicate that the project is normal.

The packages (including war and jar) are all in the target folder. Here, only jeesz-web-admin is used as an example. The screenshot is as follows:

Tomcat releases jeesz project (the release process is not detailed, everyone will do it):

The various projects are described below:

Jeesz-web-admin: Can be deployed independently (background management platform)

Jeesz-web-service: can be deployed independently (REST service platform, customers can expand Rest service according to their own business, and relevant instances have been written in it)

Jeesz-service-bookmark and jeesz-service-task are dubbo service providers (here, dubbo service project development is introduced only through collection and to-do projects. Customers can expand dubbo services according to their own business, and they can be deployed at the same time or split)

Jeesz-web-bookmark and jeesz-web-task are dubbo consumer platforms, in which the service interfaces exposed by dubbo service are: Jeesz-facade-bookmark and jeesz-faade-task (here, only collection and to-do items are used to describe how dubbo client invokes dubbo service provider. Customers can implant dubbo consumer into different projects, and only some simple configuration is needed)

Deployment conditions:

1)Execute mysql database script: jeesz.sql

Database jdbc configuration items can be referenced

2)Jeesz-web-admin can be deployed directly via tomcat

Login Username Password: jeesz/admin

3)Jeesz-web-service: deployable independently via tomcat

Login Username Password: jeesz/admin

Deployment of dubbo-related projects requires the following conditions

> Install dubbo control platform, extract war package to tomcat, and replace directory with root directory, directly start tomcat (development environment provides window)

>Zookeeper registry installation, I provide zookeeper-3.4.5 version (development environment provides window), enter the installation directory to start

Reminder: I have provided relevant programs here, in which dubbo control platform should be deployed independently on Tomcat server. This does not require high availability configuration. You can start tomcat directly. Zookeeper registry has related commands that can be run directly. If you want to deploy on linux systems, you can see the relevant documentation we provide.

5)After dubbo console and registry are started, deploy Jeesz-service-bookmark and jeesz-service-task projects to tomat at the same time (they can be deployed independently) as dubbo service providers.

6)Log in to the dubbo console to view related service information. You can see that the service you published has been controlled by the console:

http://localhost:8080/root

Direct access through the address is possible because the package name is changed to Root

Username Password: root/root

7)The Jeesz-web-bookmark, jeesz-web-task dubbo consumer project is deployed in a way that lets developers understand how services are invoked.

The installation process of the whole project ends here first. Please put all the business into development after installing the project. Because the project is based on driver development, design your table well. All the controller, service, dao, xml, jsp interfaces are automatically generated by the gen code generation module of jeesz-web-admin project, and the business is directly written. The document will be continuously improved in the near future, please pay attention to it at all times.

Willing to understand the framework technology or source code friends directly plus please (penguin): 2042849237 welcome to study together related technologies

More detailed source code reference source: http://×××/technology

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.