Use of Message beans ?

[AlistairMonkeyFinger]

Hi all,

i have an application currently running where a client app is talking to a number of session beans on a single app server. i need to extend the functionality to interface another non-java application i have running on a different server. Unfortunatley this other application can only can handle one request at a time in a synchronous manner but i will have multiple users submitting jobs concurrently.

So what i need is someway on the app server to queue these jobs up before sending them to this other app. What would also be nice is to tell the users how many jobs are waiting in the queue.

So, what is the answer ? Could i acheive this by using a message EJB alone ? Or do i have to look at something more sophisticated like JMS ?

Thanks for any help and advice you may have



Alistair

 

[sedj]

I see no point in using JMS if you don't know it, or don't really know it. Plus, the MessageDrivenBean (MDB) in EJB2.0 can achieve similar results. You probably don't even need a MDB, just a normal persistent EJB would do the trick. Its easy to make a queue, just have a static Vector or other hash object (make sure its synchronized) that you can add orders to, and remove to run in your synchronous manner.

If you've got a bit of time, you could write a lovely queue with JMX - it would map to queue scenario perfectly, and is completely dynamic. Lovely stuff.

http://java.sun.com/products/JavaManagement/