Monday, November 8, 2004 12:50 AM
An MDB is a cross between a stateless session bean and a JMS client. This make the approach immensely scalable. On top of this, you can adopt a federated J2EE server deployment to add geographical scalability.
The scenario you adopt depends on the technology deployed on the client side. For instance, if your (web) client is deployed using HTML/JSP/Servlet technology, then you would have the processing servlet drop the form data into a point-to-point queue. The MDB's simply process the items from the queue.
If your client uses ASP/.NET technology you need an appropriate hook onto to the JMS service (and may the almighty grant peace to your soul :-P )