Ok, sorry for the delay in posting this reply. This issue turned out to be a
configuration error in the ra.xml. I had the wrong value in the
messagelistener-type value. Once that was fixed everything deployed fine. I
was even able to include the data source in the ear and have everything
de
The MDB is packaged in the ejb.jar. It is done with annotations, so there is
no ejb-jar.xml.
For the deployment issue, I read all of the posts about fixing the code for
deployment ordering and then added the strict to
the jboss-app.xml. And the modules are listed in the application.xml like s
"ewinston" wrote :
| The ra.rar just contains the ra.xml and the manifest Class-Path refers to
lib/logic.jar. The ejb.jar also uses lib/logic.jar, and the definition of the
MDB is within this jar. I sorted out the deployment issues around ordering, so
I know the deployment order is not a pr
Just a bit more information, in case it is pertinent and not obvious. The rar
is an inbound resource adapter that sends its messages to the MDB in the
ejb.jar. It looks like the rar is not completely deployed (in that the
classloader hasn't been set up) by the time the ejb.jar starts it's depl
