You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 30, 2019. It is now read-only.
The EJB 3.2 specification does not define a standard way to associate a JMS MDB (or any other type of MDB) with a resource adapter. Instead, if the application requires that a particular resource adapter be used, and the application server does not use it by default, then the application must specify this in the app-server-specific deployment descriptor (e.g. glassfish-ejb-jar.xml.
It is therefore proposed that a standard way is defined to associate a JMS MDB (or any other type of MDB) with a resource adapter, using either ejb-jar.xml or the MessageDriven annotation.
Affected Versions
[3.2]
The text was updated successfully, but these errors were encountered:
The EJB 3.2 specification does not define a standard way to associate a JMS MDB (or any other type of MDB) with a resource adapter. Instead, if the application requires that a particular resource adapter be used, and the application server does not use it by default, then the application must specify this in the app-server-specific deployment descriptor (e.g. glassfish-ejb-jar.xml.
It is therefore proposed that a standard way is defined to associate a JMS MDB (or any other type of MDB) with a resource adapter, using either ejb-jar.xml or the MessageDriven annotation.
Affected Versions
[3.2]
The text was updated successfully, but these errors were encountered: