Spring是独立的还是Tomcat？

Question

I am seeking for the advantages of having Spring deployed on Tomcat rather then have it out side of any application server container.

My project doesn't require any web support. It does requires technologies like transactions management, DB pool, JMX, low latency and more common java-ee technology.

So why would I use tomcat anyway? if it's just because of the reason of having DB POOL, I could implement it myself. I am looking for low latency solution.

Again, my project is a total backend no need of any web support.

So what do I miss here?

Answer 1

What do you actually mean by "more common Java EE technology"?

If it's "just a back end", what is the front end? How will applications talk to the back end?

If there's no need for a web interface, there's no advantage to using a web container.

If you have complex transaction management needs, need message queues, etc. that may be easier to set up under an application server (as opposed to a web container) because there are existing admin/management interfaces. All those may also be set up on their own, but can be more of a pain--using Spring may mitigate that pain somewhat.

The need for "more common Java EE technology", however, makes me a little nervous about implementing a standalone app, though. App containers have all that "common Java EE technology" built-in, tested, and functional. If you're bolting a variety of packages together to give you "common Java EE technology", without using a common Java EE app container, it's likely easier to just use an app container, which also gives you the benefit of providing normalized access to your services from a variety of sources.

Answer 2

If your app is not a web app, you can use any of the non-web specific application contexts listed under All Known Implementing Classes here . You can then init the context from a main method in a runnable jar.

Answer 3

If you don't need web support, you don't have to use tomcat or any other app server. Spring will provide you with most of the features you need. For connection pool, there are many options available such as c3p0 & apache dbcp. You can use one of them.

The only thing you have to worry about is a clean shutdown of your process. You can do that by implementing your own shutdown hook.

Answer 4

One of the reasons to deploy the application in tomcat is that it will provide you all of the connection burden, thread management and so on. Nothing that you could not implement yourself. But bear in mind that tomcat is robust, and they already deal with all of the troubles of implement that logic.

Besides of that there is little point in use an application container (if you think that not having to develop and maintain that amount of code is easy).

Answer 5

You shouldn't use tomcat or anything else. Spring is container already. Init spring in one simple thread, makes sure it has proper clean up flow. and that's all. I used to work on several server side integration application which do allot, communicate over different protocols to other server, and everything was easily done with out Web Containers or J2ee Application Servers. Spring have support for almost everything, sometimes with 3d party libs(caching, transactions, pools, etc ....) Simplified version could be like :

...
pubcic static  void main (String args[]){
 Server.server = new Server(...);
 server.initSpringContext()
 server.keepAlive();
 server.cleanupResources();
}

..
abstract class Server{

abstract void initSpring();
abstract void cleanUpResources();
abstract void shutdown(){
  this.state = STOP;
};
public void keepAlive()
 while(state!=STOP){
  sleep(1000)
 }

}