What 'application server should I use' ? Not so complicated app, transforming data, sending data

I'm writing some application that will work in a background (windows service? maybe some application server?) Application receives some data, then it tra开发者_运维百科nsforms/packs/optimizes in another thread and then in another thread it sends data to next server (using WebServices). There will be thick client (probably Swing) for monitoring whole process thru WebServices. All application will be written by my team (so there is no need to use complicated integration services). Application will be composed from loosely coupled classes (simple DI pattern), maybe JMS will be helpful ?

I'm wondering what technologies should I use. Tomcat? Glassfish? or maybe something lighter ? Spring server?

---

You doesn't need any application server. Keeping it as much light weight as possible is a good choice. My suggestion for you is to use a lightweight framework that supports DI, transformations, threading/seda and integration (invoking weservices) out of the box, so that you can concentrate on your application logic. The frameworks like Apache Camel, Mule etc are good candidates.

---

Tomcat is not an application server. I have never heard of spring server.

here is a list of java application servers .

The most widely used are JBoss and Glassfish.