Announcement Announcement Module
Collapse
No announcement yet.
JMS and Spring integration Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • #16
    It's been available since 2.1.0.

    Code:
    				<xsd:attribute name="destination-expression" type="xsd:string">
    					<xsd:annotation>
    						<xsd:documentation>
    A SpEL expression to be evaluated at runtime against each Spring Integration Message as
    the root object. The result should be either a Destination instance or a String representing
    the destination name. In the latter case, it will be passed to this adapter's DestinationResolver.
    If the evaluation result is null, messages will be sent to the default destination of the
    underlying JmsTemplate. This attribute is mutually exclusive with 'destination' and 'destination-name'.
    						</xsd:documentation>
    					</xsd:annotation>
    				</xsd:attribute>
    You likely have an old version of the 2.1 schema cached in STS.

    Try the following

    Window | Preferences

    Type 'cache' in the filter; in General | Network Connections | Cache, click 'Remove All'.

    Also, be sure to enable 'Spring Project Nature' on the project (right click Spring Tools...).

    Finally, ensure that 'Load NamespaceHandlers and XSDs from project's classpath' is checked in

    Window | Preferences | Spring | Beans Support | Namespaces

    and is not overridden in the project's properties.

    You may need to clean all projects after doing all this.

    Comment


    • #17
      Thanks. I am able to use "destination-expression" in <jms:outbound-channel-adapter/> and change the destination dynamically. However, it would have been really good if we could do this functionality using "int-jms:inbound-gateway".

      Comment

      Working...
      X