<div>
<br />
JMS is Java API which allows to send and receive messages between the <br />
java cprograms; see general description here<br />
<a href="http://en.wikipedia.org/wiki/Java_Message_Service" rel="ugc">http://en.wikipedia.org/wiki/Java_Message_Service</a><br />
<br />
as opposed to calling methods of the objects sending essages like in real life do not require<br />
synchronous execution (this moment presence) - you'd normally sed the message and when that<br />
your addresse picks up the message then it would send you an answer as opposed to calling the method<br />
which normally implies immediate execution.<br />
So JMS defines various object like the queue of messages, etc.<br />
and like any other API defines methods of these objects which faciolitie this process of communication.<br />

</div>



JMS is Java API which allows to send and receive messages between the
java cprograms; see general description here
http://en.wikipedia.org/wiki/Java_Message_Service [http://en.wikipedia.org/wiki/Java_Message_Service]

as opposed to calling methods of the objects sending essages like in real life do not require
synchronous execution (this moment presence) - you'd normally sed the message and when that
your addresse picks up the message then it would send you an answer as opposed to calling the method
which normally implies immediate execution.
So JMS defines various object like the queue of messages, etc.
and like any other API defines methods of these objects which faciolitie this process of communication.


<div>
<div class="content wysiwyg-content">
i would like to know differences between JMS and MDB(message driven bean). Advantages, disadvantages, uses, comparisons of each other. when, where, how, why we use them. thanks in advance
</div>
</div>


i would like to know differences between JMS and MDB(message driven bean). Advantages, disadvantages, uses, comparisons of each other. when, where, how, why we use them. thanks in advance

JMS vs MDB

Java Enterprise Edition (Java EE) is a specification defining a collection of Java-based server and client technologies and how they interoperate. Java EE specifies server and client architectures and uses profiles to define technology sets targeted at specific classes of applications. All Java EE profiles share a set of common features, such as naming and resource injection, packaging rules and security requirements.

Java EE

JavaServer Pages (JSP) allow the development of dynamically generated web pages. It uses the Java programming language; JSP pages are translated into servlets at runtime, with each servlet being cached and reused until the JSP is modified. JSP allows Java code to be interleaved with static web markup content, so the resulting page can be compiled and executed on the server to deliver the content.

Java is a platform-independent, object-oriented programming language and run-time environment, designed to have as few implementation dependencies as possible such that developers can write one set of code across all platforms using libraries. Most devices will not run Java natively, and require a run-time component to be installed in order to execute a Java program.