Announcement Announcement Module
Collapse
No announcement yet.
JMS outbound-channel-adapter with destination-resolver Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • JMS outbound-channel-adapter with destination-resolver

    I'm using spring-integration-1.0.3.RELEASE and having difficulty with the JMS outbound-channel-adapter configuration. When I configure the adapter using a connection-factory, destination-name and destination-resolver, it appears that the destination-resolver property is ignored. The destination name does not get resolved.

    Code:
    <outbound-channel-adapter channel="channel1" destination-name="queue1" destination-resolver="jmsDestinationResolver" connection-factory="jmsConnectionFactory" />
    However, if I configure a JmsTemplate bean with these same properties and then configure configure the adapter with the template, then the destination name does get resolved.

    Code:
    <outbound-channel-adapter channel="channel1" jms-template="queue1Template" />
    <bean id="queue1Template" class="org.springframework.jms.core.JmsTemplate">
        <property name="defaultDestinationName" value="queue1" />
        <property name="destinationResolver" ref="jmsDestinationResolver" />
        <property name="connectionFactory" ref="jmsConnectionFactory" />
    </bean>
    Shouldn't these two configurations have the same behavior?

  • #2
    I've got the same problem.
    The error return is

    Code:
    This destination does not exist !QUEUE.myTopic
    Like it wrote in Javadoc, this is because topic is not found

    Code:
    setReplyDestinationName
    
    public void setReplyDestinationName(java.lang.String replyDestinationName)
    
        Set the name of the JMS Destination from which reply Messages should be received. If none is provided, this gateway will create a TemporaryQueue per invocation.
    Nobody has i suggestion ??

    Comment


    • #3
      solved

      add this property to force topic instead of queue

      Code:
      <property name="pubSubDomain" value="true"/>

      Comment

      Working...
      X