Details
-
Bug
-
Resolution: Done
-
Major
-
JBossAS-4.0.0 Final
-
None
Description
I use ejb-jar.xml with EJB spec 2.1.
Jboss ignores the message-selector on the following MDB:
<message-driven >
<description><![CDATA[]]></description>
<ejb-name>TransactionWriterBean</ejb-name>
<ejb-class>com.ftisoft.streetlamp.ejb.TransactionWriter</ejb-class>
<messaging-type>javax.jms.MessageListener</messaging-type>
<transaction-type>Container</transaction-type>
<message-destination-type>javax.jms.Topic</message-destination-type>
<activation-config>
<activation-config-property>
<activation-config-property-name>destinationType</activation-config-property-name>
<activation-config-property-value>javax.jms.Topic</activation-config-property-value>
</activation-config-property>
<activation-config-property>
<activation-config-property-name>messageSelector</activation-config-property-name>
<activation-config-property-value>streetlampWritten <> true</activation-config-property-value>
</activation-config-property>
</activation-config>
<resource-ref >
<res-ref-name>jdbc/HibernateFactory</res-ref-name>
<res-type>net.sf.hibernate.SessionFactory</res-type>
<res-auth>Container</res-auth>
</resource-ref>
</message-driven>
Furthermore I see the following Warnings during deployment:
11:14:34,971 WARN [JMSContainerInvoker] No message-driven-destination given; using; guessing type
11:14:35,142 WARN [JMSContainerInvoker] No message-driven-destination given; using; guessing type
11:14:35,365 WARN [JMSContainerInvoker] Could not determine destination type, defaults to: javax.jms.Topic
11:14:35,691 WARN [JMSContainerInvoker] No message-driven-destination given; using; guessing type
11:14:35,717 WARN [JMSContainerInvoker] No message-driven-destination given; using; guessing type