As a test could you try the following:
1) Move the RAR out of the EAR file and deploy it as a standalone adapter
2) Keep the jar with the message-listener-type in the RAR file standalone deployment.
3) Deploy the MDB either in an EAR or as a standalone ejb jar file.
Also, could you post your jboss.xml file that you are using to tie the MDB to the adapter.
Also, make sure the jar that contains the message-listener is reference from the MANIFEST.MF of your ejb.jar file as well for the internal EAR deployment.
I'd rather avoid deploying the rar separately, because it needs quite a few things that are part of the ear. I don't want to have to deploy many different files.
I give you more details about the content of the ear:
- InputDriver.jar contains the message-listener interface, as well as other classes needed by the rar
- InputDriver.rar is the resource adapter
- RawProtocolService.jar contains the MDB that implements the message-listener interface, and its manifest points to InputDriver.jar in this way: "Class-Path: InputDriver.jar"
jboss.xml for the MDB is this:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE jboss PUBLIC "-//JBoss//DTD JBOSS 4.0//EN" "http://www.jboss.org/j2ee/dtd/jboss_4_0.dtd">
I ran a simple test with your configuration and I am not seeing the error.
What version of JBoss are you using?
I'm using 4.0.2.
Did you try to deploy, stop the MDB with JMX console, and restart it?
I did not test against 4.0.2, I used 4.2. I will set that up.
4.0.2 (no patches applied) works without error as well.
If you can send me your email I can forward you the project I am using to test this. Maybe we can find the difference between the two.
I tried your project, and it works fine for me too on both version of jboss (4.0.2 and 4.2.0)
I cannot see any difference in the structure of the ear nor in the descriptors.
Is there anything else we can try?
Nothing really jumps out at me. The only thing I can think of is if your listener interface is referencing classes that cannot be found. Can you check this?