On Wed, Jun 10, 2009 at 10:42 PM, sgargan wrote:
>
> In the 1.6 codeline it was possible to define routebuilders as beans in a
> Spring context and have them wired into the camel context upon intialization
> e.g.
>
>
>
> This bean would have been added to the context when the following block of
>
Hi,
Does the example, Split aggregate request/reply sample, at
http://camel.apache.org/splitter.html only work for Camel 2.0? I'm using
camel 1.5.2 and I simply get the last split message returned to the caller,
rather than the output from my custom aggregator. Looks like this was a
defect in 1
In the 1.6 codeline it was possible to define routebuilders as beans in a
Spring context and have them wired into the camel context upon intialization
e.g.
This bean would have been added to the context when the following block of
code in in the installRoutes method of the CamelContextFactoryB
Can you try out the Camel 2.0-SNAPSHOT?
Since we did some refactoring and clean up work on the camel-cxf in
Camel 2.0, maybe this bug is ready fixed in Camel 2.0-SNAPSHOT.
I will run the MTOM tests on Camel 1.x branch tomorrow.
BTW, Hadrian is doing the Camel 2.0-m2 release this week, don't hesit
I am not so sure about that. I had the same thoughts more than a year
ago, but I came to the conclusion that it's best the way it is,
although a bit confusing at times for the beginner.
A bit of background on this. Initially Camel did not have explicit
Block processors. A Block processor
I would suggest @deprecating it for the 2.0 release and work to remove them
all by 2.1 (or even if they were all removed, a .t least let users have some
time to make the migration)
On Jun 10, 2009 3:12 AM, "Claus Ibsen" wrote:
Hi
I just did a quick grep for "AndHeader" in unit tests.
We use it
On Wed, Jun 10, 2009 at 1:46 PM, Roman
Kalukiewicz wrote:
> BTW The message in the Exception could be more clear. It is not
> obvious what "Root node with no active block" is ;)
Yeah I have been wondering if we should force a begin DSL for the few
EIP types that have nested routes,
to easier pair b
BTW The message in the Exception could be more clear. It is not
obvious what "Root node with no active block" is ;)
Roman
2009/6/10 Claus Ibsen :
> On Wed, Jun 10, 2009 at 1:09 PM, Peter Maas wrote:
>> Hi,
>>
>> I wondered what the purpose of the 'end' method in a route is. I sort of
>> expected
On Wed, Jun 10, 2009 at 1:09 PM, Peter Maas wrote:
> Hi,
>
> I wondered what the purpose of the 'end' method in a route is. I sort of
> expected it to be a terminator for dead-end routes. But that doesn't seem to
> be the case.
>
> If I do something like this:
>
> from("direct:start")
> .pro
Hi,
Thanks for the response on this.
I have been using 1.6.0 version of camel. Let me know were you able to
replicate the problem at your end.
Thanks,
Trivedi
willem.jiang wrote:
>
> Hi,
>
> Which version of Camel are you using ?
> I just write a simple test on the latst Camel trunk (2.0-SNA
Hi,
Which version of Camel are you using ?
I just write a simple test on the latst Camel trunk (2.0-SNAPSHOT).
There is no exception with the "MESSAGE" dataFormat.
Willem
trivedi kumar b wrote:
> Hi,
>
> I have been trying to create a webserive using CXF by enabling MTOM option
> and setting th
Hi,
I wondered what the purpose of the 'end' method in a route is. I sort
of expected it to be a terminator for dead-end routes. But that
doesn't seem to be the case.
If I do something like this:
from("direct:start")
.process(new Processor(){
public void process(Exc
On Wed, Jun 10, 2009 at 11:10 AM, ErwinK wrote:
>
> Hi,
>
> When I have the following route:
>
> from("timer://timer?period=360")
> .to("ldap:ldapConnection?base=&scope=subtree")
> .splitter(body(List.class), new MyAggregationStrategy())
> .filter(some expression)
> .end()
> .to("smtp://mail.ho
Hi
The ticket to track this issue is at:
https://issues.apache.org/activemq/browse/CAMEL-1691
On Wed, Jun 10, 2009 at 11:26 AM, Claus Ibsen wrote:
> On Wed, Jun 10, 2009 at 11:10 AM, ErwinK wrote:
>>
>> Hi,
>>
>> When I have the following route:
>>
>> from("timer://timer?period=360")
>> .to("
On Wed, Jun 10, 2009 at 11:10 AM, ErwinK wrote:
>
> Hi,
>
> When I have the following route:
>
> from("timer://timer?period=360")
> .to("ldap:ldapConnection?base=&scope=subtree")
> .splitter(body(List.class), new MyAggregationStrategy())
> .filter(some expression)
> .end()
> .to("smtp://mail.ho
Hi
I just did a quick grep for "AndHeader" in unit tests.
We use it 554 times. So it will affect many files if we do a rename.
On Sat, Apr 4, 2009 at 8:38 AM, Ryan Gardner wrote:
> The requestBody method makes sense (it requests a body) - but
> "requestBodyAndHeader" and "requestBodyAndHeaders"
Hi,
When I have the following route:
from("timer://timer?period=360")
.to("ldap:ldapConnection?base=&scope=subtree")
.splitter(body(List.class), new MyAggregationStrategy())
.filter(some expression)
.end()
.to("smtp://mail.host.com?from=m...@host.com&to=m...@host.com");
Now, when a message
Hi
JMSReplyTo is a feature in JMS so you can also google and read about
it in general.
It is used to specify a destination name in which a receiver can send
back a reply to the original sender.
As JMS is async you kinda like the regular postal service have to
write a postal adr. the receiver can
On Tue, Jun 9, 2009 at 5:02 PM, hans couder wrote:
> Hi,
>
>
> I'm using for my camel project the Scala DSL and would like to create some
> routes for testing in scala.
> Is there a scala version of CamelTestSupport or the camel-test module?
Not that I know of. As they are pure Java you should be a
19 matches
Mail list logo
