-
1. Re: MDB deploy fails, tricky JMSContainerInvoker
pra Feb 3, 2002 4:41 PM (in response to garyaiki)Can't remember any QueueConectionFactory tag in vanilla ejb-jar. How does your desployment descriptor look?
//Peter -
2. Re: MDB deploy fails, tricky JMSContainerInvoker
garyaiki Feb 3, 2002 5:48 PM (in response to garyaiki)//ejb-jar.xml
<message-driven>
<ejb-name>batch-MDB</ejb-name>
<ejb-class>
com.x.domain.query.results.batch.BatchMSGBean
</ejb-class>
<transaction-type>Container</transaction-type>
<message-driven-destination>
<destination-type>
javax.jms.Queue
</destination-type>
</message-driven-destination>
</message-driven>
//jboss.xml
<message-driven>
<ejb-name>batch-MDB</ejb-name>
<destination-jndi-name>
JobJMSQueue
</destination-jndi-name>
</message-driven>
//jboss.jcml
//
Thanks, Gary -
3. Re: MDB deploy fails, tricky JMSContainerInvoker
pra Feb 4, 2002 3:32 AM (in response to garyaiki)From the manual: all destinations are prefixed with either topic or queue:
"queue/JobJMSQueue" should be the name.
That should do the job (I hope).
//Peter -
4. Re: MDB deploy fails, tricky JMSContainerInvoker
garyaiki Feb 4, 2002 11:03 PM (in response to garyaiki)Thanks Peter,
Changing jboss.xml from
<destination-jndi-name>
JobJMSQueue
</destination-jndi-name>
to
<destination-jndi-name>
queue/JobJMSQueue
</destination-jndi-name>
Did not solve the problem, incredibly, what solved it was changing ejb-jar.xml from
<destination-type>
javax.jms.Queue
</destination-type>
To
<destination-type>javax.jms.Queue</destination-type>
It was choking on whitespace! What kind of parser is this? -
5. Re: MDB deploy fails, tricky JMSContainerInvoker
pra Feb 5, 2002 3:03 AM (in response to garyaiki)It's probably not the parser (crimson) but the XML helper methods in JBoss that does not trim whitespace. Nice that it works.
//Peter