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

William McDonald commented on CAMEL-5510:
-----------------------------------------

I can't get to it now, so if you think you can close it that's fine.  If 
it comes up again, we can always readdress it then.

William McDonald
Sr. Software Developer   |  TransCentra, Inc.
Office: 1-602-635-5910  |   Mobile: 1-602-741-3664  | 
[email protected]   |   www.TransCentra.com
Regulus Group and J&B Software are now TransCentra

This email message is intended for the named recipient only and may be 
privileged and/or confidential. If you are not the intended or named 
recipient or have received this email in error then you should delete this 
email and you should not copy, forward or disclose it to any other person. 
The views and opinions expressed in this email are those of the sender and 
may not represent the views and opinions of TransCentra



From:   "Christian Posta (JIRA)" <[email protected]>
To:     [email protected], 
Date:   09/18/2013 02:19 PM
Subject:        [jira] [Commented] (CAMEL-5510) Competing Consumers fails 
for jms queue using AdviceWith




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

Christian Posta commented on CAMEL-5510:
----------------------------------------

I can confirm these tests pass on master.

I think we should close this and reopen if reporter can reproduce on 
latest snapshots.
 
CompetingConsumersDoesNotWork.java, CompetingConsumersWorks.java
endpoint is a jms queue, so it should be able to have multiple consumers 
attach to it.  When I use the standard CamelTestSupport methodology and 
let it create and start my context, mock my out points, etc. everything 
passes (see CompetingConsumersWorks.java).  However when I try and use the 
strategy of not letting the junit support create everything, ie. 
doesn't pass (see CompetingConsumersDoesNotWork.java).  I can actually get 
it to work, but only if I start the context before adding the second set 
of routes to the context (see comments in code). 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA 
administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


                
> Competing Consumers fails for jms queue using AdviceWith
> --------------------------------------------------------
>
>                 Key: CAMEL-5510
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5510
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-test
>    Affects Versions: 2.9.2
>         Environment: Windows7 x64 Juno Eclipse
>            Reporter: William McDonald
>            Assignee: Claus Ibsen
>            Priority: Minor
>         Attachments: CompetingConsumersBase.java, 
> CompetingConsumersDoesNotWork.java, CompetingConsumersWorks.java
>
>
> I was trying to test two routes that start from the same endpoint.  The 
> endpoint is a jms queue, so it should be able to have multiple consumers 
> attach to it.  When I use the standard CamelTestSupport methodology and let 
> it create and start my context, mock my out points, etc. everything passes 
> (see CompetingConsumersWorks.java).  However when I try and use the strategy 
> of not letting the junit support create everything, ie. 
>         public boolean isUseRouteBuilder() { return false; } 
>         public boolean isUseAdviceWith() { return true; } 
> and try and use AdviceWithRouteBuilder to mock out routes the test doesn't 
> pass (see CompetingConsumersDoesNotWork.java).  I can actually get it to 
> work, but only if I start the context before adding the second set of routes 
> to the context (see comments in code).   

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to