Hi George!
Short answer is as it pertains to the MessageListener interface, they are
two sides of the same coin. Not my best presentation ever, but the first
half of this goes into API-level detail on the internals.
-
https://www.parleys.com/tutorial/java-ee-7-infinite-extensibility-meets-infinite-reuse
This talk is pre EJB 3.2. The proposal mentioned did get into EJB 3.2,
unlocks some potential for JMS to have an annotation-driven MDB API, and is
likely what your friend is talking about.
The state of all this is we got the simplification into EJB 3.2 and now we
need to finish the other side of the coin (JMS MDBs).
-David
On Sun, Apr 26, 2015 at 11:52 AM, George Karabotsos <karabot_at_gmail.com>
wrote:
> Thank you for all the replies!
> Reading through the fifth chapter of the EJB 3.2 Spec I see similarities
> with JMS. Unfortunately, I can't tell where the similarities begin and
> end, so I will ask a question knowingly in ignorance :).
>
> What is the difference between a MDB and JMS?!
>
> Cheers,
> George
>
> On Sat, Apr 25, 2015, at 09:21 PM, Clebert wrote:
> > Arrays of messages (batching) would be a great add on ;)
> >
> > -- Clebert Suconic typing on the iPhone.
> >
> > > On Apr 24, 2015, at 18:49, <karabot_at_gmail.com> <karabot_at_gmail.com>
> wrote:
> > >
> > > Hello fellow JMS users.
> > >
> > > Is there such a feature that will allow for a class to receive messages
> > > without implementing the MessageListener interface?
> > >
> > > Going though the JMS Spec 2.0 I see no such indication.
> > >
> > > I am only asking because one of my colleagues was claiming such a
> > > feature does exist.
> > >
> > > Cheers,
> > > George
>