Here you can see an example of BlazeDS JMS configuration settings in Message_config.xml
<destination id=”MessageDestination”>
<properties>
<jms>
<destination-type>Topic</destination-type>
<message-type>javax.jms.TextMessage</message-type>
<connection-factory>ConnectionFactory</connection-factory>
<destination-jndi-name>topic/updateTopic</destination-jndi-name>
<delivery-mode>NON_PERSISTENT</delivery-mode>
<message-priority>DEFAULT_PRIORITY</message-priority>
<acknowledge-mode>AUTO_ACKNOWLEDGE</acknowledge-mode>
<transacted-sessions>false</transacted-sessions>
<initial-context-environment>
<property>
<name>Context.SECURITY_PRINCIPAL</name>
<value>admin</value>
</property>
<property>
<name>Context.SECURITY_CREDENTIALS</name>
<value>admin</value>
</property>
<property>
<name>Context.PROVIDER_URL</name>
<value>jnp://localhost:1099</value>
</property>
<property>
<name>Context.INITIAL_CONTEXT_FACTORY</name>
<value>org.jnp.interfaces.NamingContextFactory</value>
</property>
</initial-context-environment>
</jms>
</properties>
<adapter ref=”jms”/>
</destination>
Remember to use ConnectionFactory class rather using TopicConectionFactory class for the tag <connection-factory>.
Hi Nagesh,
apparently you have your JBoss up and running. I am stuck with mine, maybe you have a place to start. I have a BlazeDS instance next to JBoss. I used your settings (apart from the topic/updateTopic that is the default topic/testTopic) and everything starts up flawlessly. Exept that I do not get any messages from the JBoss server to the Flex client. In the DS-console I can see the JMSAdapter being active but the service message count stays at 0.
Apparently my JMS client (BlazeDS) is listening but it receives no messages from the JBoss instance. I appreciate your post and now that I am reading my reply, I recognize that you can hardly answer me
regards, Jelle
Comment by Jelle van Wieringen — November 25, 2008 @ 4:33 pm