-
1. Re: Message Driven Bean Pojo using JCA 1.5 inflow
trevorh Feb 8, 2006 5:41 AM (in response to trevorh)Just installed RC5-PDF and it works ok!!!! Thankyou
I did get the following warnings:
10:10:41,719 INFO [EARDeployer] Init J2EE application: file:/C:/Program Files/jboss-4.0.3SP1/server/default/deploy/mailserver.ear
10:10:42,329 INFO [Ejb3AnnotationHandler] found EJB3: ejbName=MailMDB, class=trevan.mailserver.ejb.MailMDBEJB3, type=MESSAGE_DRIVEN
10:10:42,329 INFO [Ejb3Deployment] EJB3 deployment time took: 516
10:10:42,501 INFO [JmxKernelAbstraction] installing MBean: jboss.j2ee:service=EJB3,ear=mailserver.ear,jar=mailserver.ejb3,name=MailMDB with dependencies:
10:10:42,939 WARN [MDB] No message-driven-destination given; using; guessing type
10:10:42,939 WARN [MDB] Could not determine destination type, defaults to: javax.jms.Topic
10:10:42,954 WARN [MDB] destination not found: topic/MailMDB reason: javax.naming.NameNotFoundException: MailMDB not bound
10:10:42,954 WARN [MDB] creating a new temporary destination: topic/MailMDB
10:10:42,970 INFO [MailMDB] Bound to JNDI name: topic/MailMDB
10:10:43,111 INFO [EJB3Deployer] Deployed: file:/C:/Program Files/jboss-4.0.3SP1/server/default/tmp/deploy/tmp60554mailserver.ear-contents/mailserver.ejb3
10:10:43,111 INFO [EARDeployer] Started J2EE application: file:/C:/Program Files/jboss-4.0.3SP1/server/default/deploy/mailserver.ear
It appears to be looking for a message-driven-destination and a destination which my custom message interface does not have. Does it need bind a JNDI name?
Thanks