Hi
Glad to report that we now have done all 4 issues on Camel 2.0 trunk.
So we can start focus on getting the remaining work done so we can get
ready for a release candidate.
On Thu, Apr 2, 2009 at 7:18 AM, Claus Ibsen wrote:
> Hi
>
> We are in the final phase of Camel 2.0 and need to get the
Hi
What remains now that must be done are:
a)
Resort stream cache. Allowing Camel to work seamless with SMX.
We might wanna enable it by default globally as for instance the
content based router with xpath predicates requires to read the XML
stream multiple times.
Even for transacted routes, so i
On Fri, Apr 3, 2009 at 3:07 PM, Claus Ibsen wrote:
> Hi
>
> Just an updated
>
> #1: DONE
> #3: DefaultErrorHandler = DONE
#3: TransactionErrorHandler = DONE
#3: DONE
>
>
> On Thu, Apr 2, 2009 at 7:18 AM, Claus Ibsen wrote:
>> Hi
>>
>> We are in the final phase of Camel 2.0 and need to get the la
Hi
Just an updated
#1: DONE
#3: DefaultErrorHandler = DONE
On Thu, Apr 2, 2009 at 7:18 AM, Claus Ibsen wrote:
> Hi
>
> We are in the final phase of Camel 2.0 and need to get the last
> features and fixes done. I have been looking at the JIRA tickets and
> moved stuff for 2.1.
>
> There are 2 i
Hi
We are in the final phase of Camel 2.0 and need to get the last
features and fixes done. I have been looking at the JIRA tickets and
moved stuff for 2.1.
There are 2 issues we must address:
===
1)
Change default error handler strategy (CAMEL-714) to no error handling at
