Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’m wondering, why not use Session Beans instead of Message Driven Beans ?
If you can call remote methods from EJBs, so why bother sending/receiving messages with Message Driven Beans (which is more difficult to develop than session beans) ?
In which scenarios Message Driven Beans become useful ?
Hmm, they don’t serve the same purpose, message-driven beans allow Java EE applications to process messages asynchronously.
Because MDBs give you asynchronism and loose coupling, which is something you might want/need in some situations:
By the way, I’ve personally always found MDBs to be the easiest Enterprise Beans to develop.
See above.
See also