Unable to deploy EJB 2.0 MDB that uses message-driven-destination in JBoss EAP 6.2

Solution Unverified - Updated -

Issue

  • Unable to deploy EJB 2.0 MDB that uses message-driven-destination such as shown below in JBoss EAP 6
<message-driven>
  <ejb-name>ExampleMDB</ejb-name>
  <ejb-class>examples.ExampleMDB</ejb-class>
  <transaction-type>Bean</transaction-type>
  <message-selector>mdbMessage</message-selector>
  <acknowledge-mode>Auto-acknowledge</acknowledge-mode>
  <message-driven-destination>
    <destination-type>javax.jms.Topic</destination-type>
    <subscription-durability>Durable</subscription-durability>
  </message-driven-destination>
</message-driven>
  • When putting in the version for EJB 2.0 it is still possible to use an element that was introduced in EJB 2.1 <message-destination-type> instead of <message-driven-destination>
    We currently use the following definition:
<!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">;

It doesn't seem to be possible to use <message-driven-destination> any longer, though EAP6 is defined as EJB 2.x-compatible (not only EJB 2.1)

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP) 6
    • EJB 2.0 MDB

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.