Use the "direct" endpoint.
On 7/14/14 1:02 PM, "srinivas_vsk" wrote:
>
>I was looking to link multiple routes together for a complex scenario,
>something like
>
>from(route1).to(route2).to(route3).to(routend)
>
>Any ideas?
>
>Thanks
>
>
>
>
>--
>View this message in context:
>http://camel.4654
Hmm I meant to link you to the *exclusive* fixed reply queue, not the
shared one.
Correct link:
http://camel.apache.org/jms.html#JMS-Request-replyoverJMSandusinganexclusiv
efixedreplyqueue
Jeff
On 7/10/14 10:24 AM, "Jeff Bischoff" wrote:
>Hi Kev,
>
>I believe you can use
Hi Kev,
I believe you can use an exclusive fixed reply queue for that.
Please see:
http://camel.apache.org/jms.html#JMS-AboutusingCameltosendandreceivemessage
sandJMSReplyTo
And especially see:
http://camel.apache.org/jms.html#JMS-Request-replyoverJMSandusingasharedfix
edreplyqueue
I've had some
?
Thank you,
Jeff
On 6/26/14 9:48 PM, "Jeff Bischoff" wrote:
>The reason I want to start the route before the whole application context
>is ready is that some of the spring-loaded services in my application
>require a request/response message to be processed by another
redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On June 27, 2014 at 5:08:36 AM, Jeff Bischoff (jbisch...@wdtablesystems.com)
wrote:
> Okay, tried the work-around we discussed and it *almost* worked...
>
> j
the context with the desired timing, but it came up with
zero routes.
Doh!
Any further ideas on the workaround, or will I need that eagerStart
feature?
Thank you,
Jeff
On 6/26/14 3:58 PM, "Claus Ibsen" wrote:
>On Thu, Jun 26, 2014 at 9:55 PM, Jeff Bischoff
> wrote:
>&
ell, so we start CamelContext sooner.
>
>Feel free to log a JIRA ticket
>http://camel.apache.org/support
>
>
>
>On Thu, Jun 26, 2014 at 8:59 PM, Jeff Bischoff
> wrote:
>> When I try this, I see the "myCamel" bean instantiated (it has been
>>pass
gs are really
starting...
How do I trigger that earlier?
Thank you,
Jeff
On 6/26/14 10:59 AM, "Claus Ibsen" wrote:
>You set the others beans to have depends-on Camel.
>
>
> ...
>
>
>
>On Thu, Jun 26, 2014 at 4:52 PM, Jeff Bischoff
> wrote:
>> I'
I'm having a problem using the Camel Spring DSL. Starting the routes seems to
be the very last thing that is done during Spring initialization.
How do I trigger Spring to fully initialize camel and all the camel routes
earlier in the Spring initialization process (i.e. before a particular other
Hello,
Has anyone seen the following error before, while working with JMS topics in
Camel?
I am using Camel to talk between a single JMS (AMQ) broker and a network of
brokers.
I have searched for answers, but apparently no one has encountered "Failed to
register topic" before.
Any help is ap
trongly recommended to either set "sessionTransacted" to "true"
>or specify an external ³transactionManager""
>
>
>On 19 Jun 2014, at 12:17 am, Jeff Bischoff
>wrote:
>
>> Same JVM, different connection factor
riber running in the same JVM and using the same
>connection factory with the same client id?
>
>On 18/06/2014, at 1:59 AM, Jeff Bischoff
>wrote:
>
>> Not using a queue, just an AMQ topic. Was working fine before I
>>introduced
>> Camel, so I think I must be mi
Java Architect @ EA*
>*Author of: Maintainable Java (Kindle
><http://www.amazon.com/Maintainable-Java-Robert-Simmons-Jr-ebook/dp/B00AKH
>I69K>)(iTunes
><https://itunes.apple.com/us/book/maintainable-java/id585666097?mt=11>)*
>*LinkedIn: **http://www.linkedin.com/pub/
e choice but send it directly to the queue without the
>> recipient list. Also enable tracing on the camel context so you can see
>> what is happening to your message each step of the way.
>>
>> On 17/06/2014, at 6:28 AM, Jeff Bischoff
>> wrote:
>>
Does nobody use Topics with Camel? They don't seem to work as expected.
JB
On 5/30/14 10:48 AM, "Jeff Bischoff" wrote:
>Correction:
>
>1) Why would *CACHE_CONSUMER* on the ActiveMQComponent cause endless
>external
>redeliveries of a (filtered out) topic message, w
Someone once told me to avoid using Spring's connection factories with
Camel. Not sure of the why though.
JB
On 6/6/14 10:14 AM, "dancsi" wrote:
>Anyone having experience with IBM/WebSphere MQ? Shall I rely on WMQ
>Connection Factory caching or shall I rather configure Spring's
>CachingConnecti
I'm trying to figure out the same thing (although I'm working with AMQ,
not IBM). Queues seem pretty straightforward, but the topics seem very
sensitive to the caching/transaction settings. Don't know the right
answer, but interested to know.
JB
On 6/4/14 10:24 AM, "dancsi" wrote:
>There is jus
For this, I have used a RoutePolicy. This lets me stop the route after the
exchange is finished.
My code looks like this (snippets):
public class MyRoutePolicy extends RoutePolicySupport
{
@Override
public void onExchangeDone(Route pRoute, Exchange pExchange)
{
super.onExchange
Have you tried stopping the Consumer on the jms endpoint? I'm no Camel
expert, but I've had more luck stopping consumers than stopping routes.
JB
On 5/30/14 4:09 PM, "rkjoshi2" wrote:
>I have an apache-camel JMS route.
>
>form("jms:queue:sourceQueue").to("messageProcessor")
>
>My requirement is
Correction:
1) Why would *CACHE_CONSUMER* on the ActiveMQComponent cause endless
external
redeliveries of a (filtered out) topic message, when with other cache
settings (like CACHE_SESSION) this does not occur?
On 5/30/14 10:39 AM, "Jeff Bischoff" wrote:
>Maybe I need to narrow
provide enough info below to answer these questions? Topics just
aren't working in Camel the way that I would expect!
Thanks,
Jeff Bischoff
WDTS
On 5/29/14 4:25 PM, "Jeff Bischoff" wrote:
>Hi all,
>
>Please forgive me if this is a basic question.
>
>Working with C
"projectx.>" appearing and
disappearing in the list rapidly. I assume that's caused by the Camel polling
frequency. It seems a little disturbing to me; is that normal?
Thanks so much for taking the time to help!
Jeff Bischoff
WDTS
22 matches
Mail list logo
