Topic of graduation Design

I received the news from the college today that I had to prepare for the graduation project. As for the topic, you can decide for yourself, or it can be determined by the teacher.

Because I still will have some things, do not want to do some useless things to waste time, so I think I would like to do something meaningful, since the time spent, try to make it valuable.

From the past to do, the more is to do a project (or where to find a program to change the finished), but the project I think it has done enough, the main thing is that there is nothing in the mind that I want to do very much. Recently in the work I also encountered some problems, so I am prepared to tidy up, some can be standardized, the process of things as far as possible to make a fixed set of tools, or is a template. This will often be used in future work, to facilitate their own and others (if someone is willing to use) development, in the long term, can be used for their own team.

So I consulted the topic of the teacher: whether you can do a set of tool templates, rather than a running program. The answer is yes, and hopefully I'll give him a reply after the subject is ready.

My idea is: 1. The project can not be useless, 2. The subject cannot be too simple, 3. It must also be within its reach,

Recent work encountered more troublesome problems are: 1. In the development process, in addition to writing some regular code, in the need to remotely invoke the new service, the database to access the new mapper in the original configuration code to add the bean. 2. After the development is completed, from the PC to the test server deployment, you need to package (related to different environment configuration files), transport, service restart and other complex steps, especially in debugging to find a bug in the phase of the need for continuous re-packaging and release.

For 1, can I make these configurations automatic, and for 2, can I write a plugin to complete the transfer from PC to server and deploy it.

For question 2, the main use of the web is the MAVEN plugin: cargo or Tomcat, and these 2 kinds of plug-ins are based on the manager in the Tomcat WebApps, it happens that our company has several servers Tomcat is not with the manager. Automating deployment is no more than two steps: 1. Transfer files, 2. Restart Tomcat. All of these seem to be achievable.

So my goal now is to build a MAVEN project, set up a variety of common configurations (Hessian calls, database access, MQ, etc.), and deploy packaged plug-ins and integration to facilitate future project development.

Although I would like to write some of the distributed tools, but now the ability to see, or wait for me to read the books at hand to say it.

Topic of graduation Design