Re: Custom AggregationStrategy needs specific headers

2009-06-12 Thread Claus Ibsen
On Fri, Jun 12, 2009 at 4:38 PM, ErwinK wrote: > > > Claus Ibsen-2 wrote: >> >> Hi >> >> I have created a ticket to track this issue >> https://issues.apache.org/activemq/browse/CAMEL-1702 >> >> We will *only* do this migration at Camel 2.0 to keep the old behavior >> in Camel 1.6.x as this branch

Re: How do i use a JMS Consumer in Camel DSL?

2009-06-12 Thread Willem Jiang
Hi It's a known issue[1], and we fixed it in SMX4 branch. If you are not comfortable with playing apache SNAPSHOT version, you can try out the coming up Fuse ESB 4.1.x monthly release version. [1] http://fusesource.com/issues/browse/ESB-733 Willem triggershot wrote: > Hey, > > i have the follo

Re: No operation found in the CXF client

2009-06-12 Thread Willem Jiang
Yeah, the behavior of the camel-1.6.1 is not right. Please feel free to create a JIRA with it. Since we have same unit tests with you use case in camel-1.x branch, and they look good, please submit a test case to reproduce this issue, so I can dig the issue sooner. Thanks for you contribution on t

Re: No operation found in the CXF client

2009-06-12 Thread ychawla
Hello All, I solved the issue on Camel 1.6.0. The solution was to add a header called operationNameSpace: http://www.wisconsin.gov/wijis/gateway/PointerUploadService/ This did the trick. My assumption was that since this message went over a JMS queue that the header called operationNameSpace wa

Re: Custom AggregationStrategy needs specific headers

2009-06-12 Thread ErwinK
Claus Ibsen-2 wrote: > > Hi > > I have created a ticket to track this issue > https://issues.apache.org/activemq/browse/CAMEL-1702 > > We will *only* do this migration at Camel 2.0 to keep the old behavior > in Camel 1.6.x as this branch is maintenance and for important bug > fixes only. > Its

Re: Custom AggregationStrategy needs specific headers

2009-06-12 Thread Claus Ibsen
Hi I have created a ticket to track this issue https://issues.apache.org/activemq/browse/CAMEL-1702 We will *only* do this migration at Camel 2.0 to keep the old behavior in Camel 1.6.x as this branch is maintenance and for important bug fixes only. Its intended for drop in replacements for produ

Re: How to prevent routes from started twice?

2009-06-12 Thread Claus Ibsen
On Fri, Jun 12, 2009 at 2:08 PM, akuhtz wrote: > > I see it twice! Once for the root application context (which is correct, > because its the context where the camel context is defined in) and a second > time for the web application context (which I think is incorrect because > it's the child conte

Re: How to prevent routes from started twice?

2009-06-12 Thread akuhtz
I see it twice! Once for the root application context (which is correct, because its the context where the camel context is defined in) and a second time for the web application context (which I think is incorrect because it's the child context of the root). I don't know if it would work in all c

Re: How to prevent routes from started twice?

2009-06-12 Thread Claus Ibsen
On Fri, Jun 12, 2009 at 1:30 PM, akuhtz wrote: > > Hi Claus, > > I does honor but the problem is that you can't start the camel context (from > another bean) if shouldStartContext is set to false, and this is the only > way to prevent the execution of code that is triggered by refresh event. > > I'

How do i use a JMS Consumer in Camel DSL?

2009-06-12 Thread triggershot
Hey, i have the following problem. I've defined a JMS - Service Unit with a Provider and Consumer (like in the Tutorial "Camel" from servicemix.apache.org): ## http://servicemix.apache.org/jms/1.0"; xmlns:tutorial="urn:org:apache:service

Re: How to prevent routes from started twice?

2009-06-12 Thread akuhtz
Hi Claus, I does honor but the problem is that you can't start the camel context (from another bean) if shouldStartContext is set to false, and this is the only way to prevent the execution of code that is triggered by refresh event. I'll create a JIRA ticket with a problem description. -- Vie

Re: Documenting the Camel DSL

2009-06-12 Thread Charles Moulliard
Hi, I agree on your remarks Christian. It is better to have a single point of entry for syntax about camel DSL language with examples than using google to find out where the info has been defined in the wiki pages of camel. Such a documentation (I will participate to enrich it) is absolutely neces

Re: Custom AggregationStrategy needs specific headers

2009-06-12 Thread ErwinK
Claus Ibsen-2 wrote: > > On Fri, Jun 12, 2009 at 12:07 PM, ErwinK wrote: >> >> Hello, >> >> I am using Camel 1.6.1. With the following route: >> >> from("timer://timer?period=1000") >> .setBody(constant("select * from table")) >> .to("jdbc:db") >> .splitter(body(List.class), new MyAggregationSt

Re: Documenting the Camel DSL

2009-06-12 Thread Christian Schneider
Claus Ibsen schrieb: So I doubt its possible to cover all languages in all DSLs. I suggest to focus solely on Spring and Java DSL. Yes .. Spring and Java DSL are the focues for me too. They are used the most. And we do not absolutely need to have samples for both. Often its possible to trans

Re: How to prevent routes from started twice?

2009-06-12 Thread Claus Ibsen
Hi Could you create a JIRA ticket for this. Camel should honor the shouldStartContext when it receives this spring refresh event. On Thu, Jun 11, 2009 at 5:33 PM, akuhtz wrote: > > Hi, > > I've a spring based web application that has 2 applicationContexts (the > second has the first as parent).

Re: Custom AggregationStrategy needs specific headers

2009-06-12 Thread Claus Ibsen
On Fri, Jun 12, 2009 at 12:07 PM, ErwinK wrote: > > Hello, > > I am using Camel 1.6.1. With the following route: > > from("timer://timer?period=1000") > .setBody(constant("select * from table")) > .to("jdbc:db") > .splitter(body(List.class), new MyAggregationStrategy()) > .to("some default componen

Custom AggregationStrategy needs specific headers

2009-06-12 Thread ErwinK
Hello, I am using Camel 1.6.1. With the following route: from("timer://timer?period=1000") .setBody(constant("select * from table")) .to("jdbc:db") .splitter(body(List.class), new MyAggregationStrategy()) .to("some default component uri that doesn't forward headers") .end() .to("log:log") The a