Announcement Announcement Module
No announcement yet.
Testing orchestration without connecting external resources Page Title Module
Move Remove Collapse
Conversation Detail Module
  • Filter
  • Time
  • Show
Clear All
new posts

  • Testing orchestration without connecting external resources

    I have a simple orchestration that receives a message through an AMQP inbound channel adapter and delivers it to one or more other AMQP outbound channel adapters depending on a given set os circumstances.

    I wan't to test this, but I don't want to depend to an external AMQP server for unit testing, so I recon a few posible solutions :

    - Split the files (one with AMQP adapters and other one with the orchestration itself), which is OK, but I'm pretty happy so far with the intergration-graph of STS and I would like to continue to use it. (STS don't support include)

    - Use the brand new bean profiles, but SI uses spring 3.0 and I think SI namespaces won't support the "profile" atribute anyway.

    - Overwrite the channel adapters with simple channels, I tried but it seems that SF will try to initialize the real adapters even if overwrited, and I don't wan't to spend the rest of the day debugging.

    If there aren't other options I will probably split the files and loose the integration-graph.

    Any suggestion?

  • #2
    Spring Integration 2.1 works fine with Spring 3.1, it just doesn't require it.

    In your POM, just <exclude/> the 3.0 version from the SI <dep>s and add 3.1 as a dependency.

    That said, using profiles, you will still lose STS integration graph support - but it is being worked on - it's in 2.9.0.RC1

    There is also a JIRA for SI visualizer multi-file support - vote it up!


    • #3
      Awesome news!

      Thanks Gary.