Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Mon, 23 Nov 2015 08:08:10 +0000 (UTC)
From: "Jonas Stein (JIRA)" <jira@apache.org>
To: issues@camel.apache.org
Message-ID: <JIRA.12915252.1448266038000.156914.1448266090935@Atlassian.JIRA>
In-Reply-To: <JIRA.12915252.1448266038000@Atlassian.JIRA>
References: <JIRA.12915252.1448266038000@Atlassian.JIRA>
 <JIRA.12915252.1448266038458@arcas>
Subject: [jira] [Created] (CAMEL-9350) Improvement of the JUnit-Tests,
 especially the property handling within a spring-boot project
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Jonas Stein created CAMEL-9350:
----------------------------------

             Summary: 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


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 {{someProperty}} 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)