Actually your application is 'tailored made' for a middleware environment. And note, but because it is a POJO now doesn't mean you have to give that up. There are varying ways to mainting POJO development in the context of an applcation server.
Interestingly enough, your application if ported would more like as not touch on just about every aspect of an EE environment
EJB -component model if you wanted declarative transactions and what not
JCA (or JBossRemoting) for bi-directional connectivity to the foreign host
JDBC -which is really JCA, for connection pools etc
So, it sounds like a pretty interesting project. Again, you wouldn't necessarily to a full scale port where you would lose the work you have already invested so no loss there.
thanks for answer. Actually, you have confirmed my thoughts on this. But if I still wanted to port the app, at least for sake of trying Jboss out, what techniques would you suggest? For sql db connection I could use entitiy beans with cmp right? But there are other issues like telnet/ssh connections to remote servers. Currently I keep these connections permanent for performance sake... I've looked at JCA and it seems to be made for 'nicer' type of data exchange, more stuctures, supporting transactions etc.
But my biggest concern is if can I use AS for deploying application that run round the clock? Or do I have to implement some mechanisms of having them run on some timer expiry?