[jira] [Resolved] (CAMEL-9350) Improvement of the JUnit-Tests, especially the property handling within a spring-boot project

["Claus Ibsen (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CAMEL-9350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-9350.
--------------------------------
    Resolution: Implemented
      Assignee: Claus Ibsen

Try with latest version. camel-spring-boot is integrated with spring property placeholders.

> Improvement of the JUnit-Tests, especially the property handling within a spring-boot project
> ---------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-9350
>                 URL: https://issues.apache.org/jira/browse/CAMEL-9350
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-spring-boot, camel-test
>    Affects Versions: 2.16.0
>         Environment: JDK 1.8-64bit, spring-boot 1.2.7, maven web project in Netbeans IDE on Windows 7 operating system.
>            Reporter: Jonas Stein
>            Assignee: Claus Ibsen
>
> Currently it is a bit complicated to test webservices, created with camel and spring boot. The main problem is to run up the whole spring/camel context with its configuration. I would like to use some annotations in the test-class and be sure that camel recognized all its routes and properties, also the possibility to use the CamelContextLifecycle would be great.
> The annotation @PropertySource should also work in JUnit-Tests to inject every property sucessfully into the 
> "two curly braces"someProperty"two curly braces" syntax. 
> Last but not least, I rather would be able to use the method whenAnyExchangeReceived of the class MockEndpoint with an exchange object as a parameter, instead of a processor.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)