Why don t you bind local threads in framework integration?

It needs to be bound to dig and search. Start the h2 bin or file on the project first, start the h2 database framework and the h2 database integration method, and create a schema directory (equivalent to a database empirical calendar) under the database

1.Frame building.

Guide the jar file from struts2 into the project. to copy the file to the src directory of the project.

Modify the file. Added: struts2

struts2

The method in is called.

Automatic method calls (only execute).

Specify the method call (via the method property in the action tag).

Dynamic method calls (at the time of calling, add after the action!) Method name, e.g. login!deletuser)

Note: Wildcard calls.

3.The way in which the action receives client parameters.

Define parameter variables directly in the action and generate set and get methods.

Define the class that receives the parameters.

Note: Both get and set methods are provided for the member variables of the action.

Let the action implement the modeldriven interface and implement the getmodel method in it.

If you use ActionContext to obtain it, all you get is a map object.

Use the servletActionContext to obtain the object based on the servlet API.

Let the action implement the requestaware, sessionaware, and applicationaware interfaces, and implement the methods inside.

5.Four steers.

action to the page (default).

action redirects to the page.

action to action

login is a good balance.

loginlogin

action redirects to action login

Write the Hibernate configuration to the Spring configuration, and use Spring to manage and call Hibernate factories and sessions, etc.

Struts are usually 2 in. One is to use a factory class in Spring instead of Struts' factory class to generate actions, and use Spring to manage them. The other is that struts generate actions in their own factory, but are managed by Spring.

This is a bit less coupled.

That's pretty much it, Hibernate takes care of what it does best, database management. The request processing of the struts page calls the corresponding underlying database, etc. Spring is in charge of managing both of them

Can't send **. You contact me to help you pass it on.

Spring AOP dependency injection is a singleton object, if we use multiple identical processing and not too time-consuming, we will generally use the for loop to execute directly, in this case, even if there is transaction management, it will not affect the business execution; However, most applications such as system-to-system interactions are time-consuming, and it is not advisable to use for loops to execute business, so we want to use threads to solve this problem.

In addition, as a side note: if you are testing under the @test provided by Spring: if there is multithreading, you need to call it; Implement thread waiting, which is also necessary to test multithreaded mode.

If you don't add threaded hibernation and don't wait for the multithread to finish, it is very likely that the processing of the multithreaded call will not be detected.

Where is the multithreading, and in what context