Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3
  • 2
    I'll add that MDBs are not necessarily asynchronous, it's really the Connector that drives the communication style. MDBs were born out of JMS and the Connector API was abstracted from that use case, but now the Connector/MDB relationship actually allows for any kind of communication. I have some ideas for EJB.next to further simplify the MDB/Connector relationship so that the Connector can supply it's own annotations that the MDB can use, making @ActivationConfig and the need for an explicit MessageListener interface irrelevant. Then things like JAX-RS could be done as a Connector/MDB. Commented Oct 1, 2010 at 19:12
  • @David That's right (I simplified considerably). And what you're mentioning is a very interesting direction. Thank you very much for sharing this, David. Commented Oct 1, 2010 at 20:12
  • Yeah, I'm kind of excited about it. Have been meaning to carve it out in a blog post, but since we're chatting I finally bit the bullet and did so bit.ly/bym3SC On a further side note, the whole "which bean type do I use" question is one I hope we can kill by basing everything on @ManagedBean and freeing people up to focus on the services they want to use and how they want their bean exposed. Commented Oct 2, 2010 at 0:00