Hello camel fans,
we are getting more an more contexts in our camel and write log files
(via log4j) from our beans and from camel internal classes.
With the increasing number of contexts and traffic its hard to read the
log file if we search an error in one special context.
Does anyone had
Whilst I can't comment on the tool itself (haven't used it before), do note
the project is inactive. There hasn't been a release for over 6 years...
Regards,
Richard
On Wednesday, January 25, 2012, Christian Müller <
christian.muel...@gmail.com> wrote:
> Today I stumbled about Clirr [1]. "Clirr i
+1
Christian
Am 25.01.2012 14:24, schrieb Hadrian Zbarcea:
A new patch release candidate apache-camel-2.8.4 is out with
approximately 88 issues resolved: improvements and bug fixes [1].
Please find the staging repo here:
https://repository.apache.org/content/repositories/orgapachecamel-132/
Likely around mid Feb. It would be preferable to not hijack this voting
thread though.
Hadrian
On 01/25/2012 01:06 PM, David Karlsen wrote:
Will there be a 2.9.1 soon as well?
2012/1/25 Hadrian Zbarcea:
A new patch release candidate apache-camel-2.8.4 is out with approximately
88 issues reso
Will there be a 2.9.1 soon as well?
2012/1/25 Hadrian Zbarcea :
> A new patch release candidate apache-camel-2.8.4 is out with approximately
> 88 issues resolved: improvements and bug fixes [1].
>
> Please find the staging repo here:
> https://repository.apache.org/content/repositories/orgapacheca
+1
On Jan 25, 2012, at 6:42 AM, Jean-Baptiste Onofré wrote:
> +1 (non binding)
>
> Regards
> JB
>
> On 01/25/2012 02:24 PM, Hadrian Zbarcea wrote:
>> A new patch release candidate apache-camel-2.8.4 is out with
>> approximately 88 issues resolved: improvements and bug fixes [1].
>>
>> Please
Hi Alexey,
a from dsl element can only be at the start of a route. So this is not
possible.
Christian
Am 25.01.2012 14:27, schrieb Alexey:
uri="activemq:PayrollOrder.Files.ToInspector.InProcess">
...
Ch
Am 25.01.2012 14:58, schrieb Claus Ibsen:
It is *not* trivial for people getting started with Camel to figure
out how to use a Spring XML file for the regular Spring stuff.
And then how to add Camel in there, and use the Java DSL.
As you need to addcom.foo or use a
etc. to link the Spring XM
Thanks for both clarifications which made it clear to me.
Babak
--
View this message in context:
http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-8-4-tp5430186p5430314.html
Sent from the Camel Development mailing list archive at Nabble.com.
On Wed, Jan 25, 2012 at 3:14 PM, Babak Vahdat
wrote:
> +1
>
> The long running CAMEL-3774 seems to be definitely fixed :-)
>
> Maybe not the right thread to ask for, but just realized it as I was walking
> through the modules of this release:
> Is there any good reason why we don't publish all the
Babak, thanks again for the camel-3774 fixes.
We publish things that are likely to be reused. We have the camel-test
kit users are supposed to use. The way we test individual components is
not necessarily relevant and it could change at any time. The camel-core
tests were there before camel-te
+1
The long running CAMEL-3774 seems to be definitely fixed :-)
Maybe not the right thread to ask for, but just realized it as I was walking
through the modules of this release:
Is there any good reason why we don't publish all the test jars by all the
modules. Currently we seem to do it only for
...
Christian, note the line that I have marked >>>
So can I do?
--
View this message in context:
http://camel.465427.n5.nabble.com/Forward-message-tp5166528p5430192.html
Sent fr
On Wed, Jan 25, 2012 at 2:41 PM, Christian Schneider
wrote:
> Am 25.01.2012 14:15, schrieb Claus Ibsen:
>
>> On Wed, Jan 25, 2012 at 1:29 PM, Christian Schneider
>> wrote:
>>>
>>> Am 25.01.2012 12:08, schrieb Claus Ibsen:
>>>
Hi
Currently we have a maven archetype named: camel-arc
+1 (non binding)
Regards
JB
On 01/25/2012 02:24 PM, Hadrian Zbarcea wrote:
A new patch release candidate apache-camel-2.8.4 is out with
approximately 88 issues resolved: improvements and bug fixes [1].
Please find the staging repo here:
https://repository.apache.org/content/repositories/orgapa
Am 25.01.2012 14:15, schrieb Claus Ibsen:
On Wed, Jan 25, 2012 at 1:29 PM, Christian Schneider
wrote:
Am 25.01.2012 12:08, schrieb Claus Ibsen:
Hi
Currently we have a maven archetype named: camel-archetype-java
Its however a Spring XML project with a Java RouteBuilder (eg Java DSL).
I woul
A new patch release candidate apache-camel-2.8.4 is out with
approximately 88 issues resolved: improvements and bug fixes [1].
Please find the staging repo here:
https://repository.apache.org/content/repositories/orgapachecamel-132/
The tarballs are here
https://repository.apache.org/content/re
On Wed, Jan 25, 2012 at 2:19 PM, Babak Vahdat
wrote:
> Hi
>
> a) Makes sense to me as the DSL there is in Java however the execution is
> through "mvn camel:run" which makes use of [1] to launch the IoC-stuff of
> Spring.
>
> b) Would be nice to provide such a one with *pure* Java-DSL & Java-Wirin
Hi
a) Makes sense to me as the DSL there is in Java however the execution is
through "mvn camel:run" which makes use of [1] to launch the IoC-stuff of
Spring.
b) Would be nice to provide such a one with *pure* Java-DSL & Java-Wiring
(No Spring). And then folks would start up Camel through using e
On Wed, Jan 25, 2012 at 1:29 PM, Christian Schneider
wrote:
> Am 25.01.2012 12:08, schrieb Claus Ibsen:
>
>> Hi
>>
>> Currently we have a maven archetype named: camel-archetype-java
>> Its however a Spring XML project with a Java RouteBuilder (eg Java DSL).
>>
>> I would like to propose that we:
>
Hi Claus,
On 25 January 2012 11:08, Claus Ibsen wrote:
> Hi
>
> Currently we have a maven archetype named: camel-archetype-java
> Its however a Spring XML project with a Java RouteBuilder (eg Java DSL).
>
I liked the idea to have a standalone archetype without any spring
> I would like to propos
Am 25.01.2012 12:08, schrieb Claus Ibsen:
Hi
Currently we have a maven archetype named: camel-archetype-java
Its however a Spring XML project with a Java RouteBuilder (eg Java DSL).
I would like to propose that we:
a)
Rename camel-archetype-java to camel-archetype-spring-java
b)
Create a new
Hi
Currently we have a maven archetype named: camel-archetype-java
Its however a Spring XML project with a Java RouteBuilder (eg Java DSL).
I would like to propose that we:
a)
Rename camel-archetype-java to camel-archetype-spring-java
b)
Create a new camel-archetype-standalone which is a pure J
Thx Claus, I think that's really good to have separated the spring
stuff as it will allow blueprint users to not depend on spring at all
at testing.
Btw, I mentioned some time ago integration tests for archetypes, so
here's a pointer:
https://github.com/apache/karaf/blob/trunk/archetypes/itest
On Tue, Jan 24, 2012 at 4:36 PM, Hadrian Zbarcea wrote:
> Ok, let me clarify, there are a few points made here. Making camel-test
> standalone w/o spring dependencies is great, we should do that. Having a
> camel-test-spring is ok too and as you mentioned the primary audience for
> that would be S
25 matches
Mail list logo
