I have a project that uses an inbound resource connector and an message driven 
bean.  I am trying to deploy these on jboss 4.2.3.  The app has the following 
layout :


  | app.ear
  |    lib/logic.jar
  |    ejb.jar
  |    ra.rar
  | 

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 problem.

When I try to deploy, I get the following message :


  | 15:17:27,806 INFO  [EJBContainer] STARTED EJB: com.my.mdb.WebAlertRAMDB 
ejbName: WebAlertRAMDB
  | 15:17:27,841 WARN  [ServiceController] Problem starting service 
jboss.j2ee:ear=ear.ear,jar=ejb.jar,name=WebAlertRAMDB,service=EJB3
  | org.jboss.deployment.DeploymentException: MessagingType 
'com.my.api.WebAlertProcessor' not found in resource deployment 
jboss.jca:service=RARDeployment,name='ear.ear#ra.rar'
  |         at 
org.jboss.resource.deployment.RARDeployment.createActivationSpec(RARDeployment.java:252)
  |         at 
org.jboss.resource.deployment.RARDeployment.internalInvoke(RARDeployment.java:218)
  |         at 
org.jboss.system.ServiceDynamicMBeanSupport.invoke(ServiceDynamicMBeanSupport.java:156)
  | 

Any clues as to what I am doing wrong?  I tried putting the class it is looking 
for in the ra.rar but that didn't help.  I also tried putting it in ejb.jar, 
again to no avail.  And I have tried putting the logic.jar at the same level as 
the modules (ejb.jar and ra.rar).

The jboss-app.xml has a custom class loader and the module order value of 
strict.  Aside from that it is empty.

Thanks,
Edward

View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4213181#4213181

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4213181
_______________________________________________
jboss-user mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/jboss-user

Reply via email to