+1
I tested this version with the Camel in Action source code and all tests
without the chapter "chapter9-xa" test succeed. This test also failed in
other versions before.
The manual is included in the distribution and looks well.
This release looks really well for me.
Thanks you Hadrian,
Christi
I have a look on the latch.await(...) calls and changed them. Running a
build at the moment to see if we really have some wrong-positiv tests...
Best,
Christian
On Thu, Mar 1, 2012 at 3:14 PM, Babak Vahdat wrote:
> Hi
>
> It seems there're still other false-positive unit tests as well one of
> w
Hello Dave!
Sorry for the late response. The issue is solved. You can find some unit
test for it in [1] and [2].
[1]
https://svn.apache.org/repos/asf/camel/trunk/camel-core/src/test/java/org/apache/camel/component/validator/ValidatorIncludeRouteTest.java
[2]
https://svn.apache.org/repos/asf/camel
Thanks, Claus. Much appreciated!
On 3/2/12 7:28 AM, Claus Ibsen wrote:
Okay I have committed a fix so the route scoped error handlers is now
removed from JMX, when removing a route.
On Fri, Mar 2, 2012 at 10:59 AM, Claus Ibsen wrote:
On Tue, Feb 28, 2012 at 10:03 PM, Matt Pavlovich wrote:
+1
On Thu, Mar 1, 2012 at 5:46 PM, Hadrian Zbarcea wrote:
> A new patch release candidate apache-camel-2.9.1 is out with approximately
> 108 issues resolved so far: improvements and bug fixes [1].
>
> Please find the staging repo here:
> https://repository.apache.org/**content/repositories/**org
Okay I have committed a fix so the route scoped error handlers is now
removed from JMX, when removing a route.
On Fri, Mar 2, 2012 at 10:59 AM, Claus Ibsen wrote:
> On Tue, Feb 28, 2012 at 10:03 PM, Matt Pavlovich wrote:
>> Hi Claus-
>>
>> I believe that, in general, more information available
I took another route (pun intended) towards it:
camelContext.getRoute( "routeId" ).getRouteContext().getRoute() which
is non-deprecated.
But I should still change .adviceWith( camelContext, new
AdviceWithRouteBuilder() which is deprecated in favour of the one
using ModelCamelContext instead.
201
Thanks Hadrian for assigning the ticket properly right before.
Babak
--
View this message in context:
http://camel.465427.n5.nabble.com/What-replaces-camelContext-getRouteDefinition-String-routeId-tp5530724p5530883.html
Sent from the Camel Development mailing list archive at Nabble.com.
Thanks, karma granted,
Hadrian
On 03/02/2012 01:03 AM, bruno.ba...@toyota-europe.com wrote:
Thanks Reuben and Hadrian!
My id is bbarin
However I've followed the instructions described at this link:
http://camel.apache.org/how-do-i-edit-the-website.html
Maybe it's the case to make this page m
And the JIRA-Ticket I did mention before has not been assigned to anybody,
however the revision making those changes point to that Ticket:
http://svn.apache.org/viewvc?view=revision&revision=1170482
Sorry but I do not get it!
Christian could you please give us any pointer about this?
Babak
--
Hi
That came along with [1]... And would have been nice to document it properly
to avoid such questions.
ModelCamelContext context = new DefaultCamelContext();
RouteDefinition routeDefinition = context.getRouteDefinition(...)
Then you should be fine.
[1] https://issues.apache.org/jira/browse/CA
On Tue, Feb 28, 2012 at 10:03 PM, Matt Pavlovich wrote:
> Hi Claus-
>
> I believe that, in general, more information available to the user via JMX
> is better. Being able to confirm everything is wired up is very valuable to
> users-- especially ones new to the framework. Using it to change valu
Hi,
Not that I can think of. That is indeed the beauty of Camel.
Components and the routing EIPs are separated, so creating components
is simple and plug transparently into the engine that Camel provides.
Having said that, you might want to look leveraging the asynchronous
routing engine in Camel
13 matches
Mail list logo
