Solution to the showcase exception in springside4

I have basically abandoned technology for three years. Now I can't say that it is not difficult to repeat it. Now the company wants to build a project, and the technical department leaders suggest using springside. I have never been in touch with technology for a long time, I am not familiar with the update and replacement in the technical field, so I downloaded springside4 from the Internet and started my research.

Springside is actually based on maven. After learning about Maven, we haven't gone into depth yet. There were a lot of explanations for all the terms I needed before, and it was a headache to look at them one by one. I used the original tapestry. At that time, I spent a lot of effort reading the original document (I still like reading their own documents. Now these documents are more and more organized). Now I want to use SSH, in fact, struts does not like it, but now it does not have the ability to compare, the project is tight, and everyone cannot learn new technologies. Although the current project may involve two people, since it takes me time to get familiar with both tapestry and struts, it is better for me to study by myself.

Too much time is wasted, and I find that I am deeply immersed in learning, and the project is not analyzed. This is a waste of time, so I started to build springside. Let's start with three examples of springside.

The first step is to run it first.

Download is very simple. After the official website is installed, JDK and Maven are installed, and environment variables can be configured. For Maven installation, there are also a lot of Maven tutorials, but you just need to download and decompress the configuration environment variables, maven has been integrated in myeclipse, and Baidu is loaded in eclipse. One of them is to change the manven installations path in preferenses to the local Maven path, this is conducive to the unification of IDE and local Maven versions.

Springside also decompress the package. The example of running it is very simple. You can also run it on your own with a Quickstart. It is also clear in https://github.com/springside/springside4/wiki/quickstart.

OK, run, database started, mini-service, mini-Web started, but showcase is an error, always Org. h2.jdbc. jdbcsqlexception: Table "qrtz_triggers" Not found. I checked the database and found these tables. I was tired for a day and couldn't find the cause. Later I found out how mentally retarded the mistake I made.

I copied three springside3 examples to the workspace and loaded them to myeclipse. Therefore, the source code and related configuration files have been read all the time, while springside4 is downloaded by myself, the running examples are in another directory, so the configuration file should be found in that directory. After reading the configuration file application. properties, we found that 4 changed the Database Configuration path in showcase, from JDBC. url = JDBC: H2: TCP: // localhost /~ /Showcase; quartz. JDBC. url = JDBC: H2: TCP: // localhost /~ /Showcase-quartz changed to JDBC. url = JDBC: H2: TCP: // localhost /~ /Showcase4; quartz. JDBC. url = JDBC: H2: TCP: // localhost /~ /Showcase-quartz4, and to look at the other two examples, found that the actual use of the database has changed. Connect quartz. JDBC. url = JDBC: H2: TCP: // localhost/~ On the H2 database /~ /Showcase-quartz4, found that there is no table, this explains the cause of the error, but the reason why the table is not created successfully, but unknown. Okay. Run the built-in SQL statement again on the H2 console.

Are you ready to study Apache Shiro as the basis for permission authentication? Are there any other better recommendations? If you want to know more, please kindly advise. I hope to learn from you and improve your communication.