Actually, the structure of the ear is:
.ear/APP-INF/lib/classes.jar (contains all .class files including the resource adapter)
.ear/logic.jar (contains business logic components)
.ear/message.jar (contains message driven beans that wil use the resource adapter)
and jboss.app.xml is:
<jboss-app> <module> <service>bluespace-ds.xml</service> </module> <module> <service>bluespace-jms-ds.xml</service> </module> <module> <service>ra-ds.xml</service> </module> </jboss-app>
and ra.xml is:
<connection-factories> <no-tx-connection-factory> <jndi-name>BlueSpace/POP3</jndi-name> <adapter-display-name>BlueSpace POP3 Adapter</adapter-display-name> <config-property name="PollingInterval" type="java.lang.Integer">60000</config-property> </no-tx-connection-factory> </connection-factories>
And where exactly in the JBoss docs or the spec for that matter
did you find APP-INF?
Dunno actually. My build script has done that for the last 2 years I guess and it has always worked. The APP-INF/lib/classes.jar contains all classes I need in the nested deployed jars. So in fact, the nested .jar (and also .war that I did not mention) only contain the deployment descriptors for the session beans.
I have made some progress since... had a typo in a setter method of one of the properties of the resource adapter. I discovered that when I used the same structure as the examples (i.e. not use nested deployment).
Currently, the app deploys but I cannot see my MDB connecting to the resource adapter, although I have logging in the activtion method.