Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Wed, 24 Aug 2011 12:19:29 +0000 (UTC)
From: "Willem Jiang (JIRA)" <jira@apache.org>
To: dev@camel.apache.org
Message-ID: 
 <803000708.9007.1314188369123.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1626911794.8907.1314184889048.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (CAMEL-4374) The debugger doesn't work in the
 CamelSpringTestSupport with route defined in XML
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CAMEL-4374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13090160#comment-13090160 ] 

Willem Jiang commented on CAMEL-4374:
-------------------------------------

@Andreas
If there are more than one camel context in the spring application context, your patch can not work for this case.
As the CamelSpringTestSupport it only try to start the first camel context, we need find other way to resolve this kind of issue.


> The debugger doesn't work in the CamelSpringTestSupport with route defined in XML
> ---------------------------------------------------------------------------------
>
>                 Key: CAMEL-4374
>                 URL: https://issues.apache.org/jira/browse/CAMEL-4374
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-test
>    Affects Versions: 2.8.0
>            Reporter: Andreas Kuhtz
>             Fix For: 2.8.1, 2.9.0
>
>         Attachments: camel-4374.patch
>
>
> The debugger doesn't work in the CamelSpringTestSupport with route defined in XML. This issue is related to CAMEL-4368 (closed and I cannot re-open).
> I've created a patch with 2 new tests that show the problem and a solution (check the doSetup() method in the tests). However I think this could be improved by moving the SpringCamelContext.setNoStart(true); to CamelSpringTestSupport).

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira