This message should be posted on the users mailing of activemq and not dev
mailing of camel.
On Mon, Sep 22, 2014 at 5:42 PM, gen.antony wrote:
> Problem Statement:
>
> Need to create dynamic topics in Websphere MQ according to the parameter
> CustomerName and Date. Thats is
The Apache Jenkins build system has built Camel.2.13.x.notest (build #67)
Status: Still Failing
Check console output at https://builds.apache.org/job/Camel.2.13.x.notest/67/
to view the results.
I would avoid to OSGIfied jruby-core and jruby-stdlib because
jruby-complete is already an OSGI bundle.
I will update to jruby-complete when 1.7.16 is available.
Best,
Christian
-
Software Integration Specialist
Apache Member
V.P. Apache Camel | Apache Camel PMC Member | Apache C
Github user asfgit closed the pull request at:
https://github.com/apache/camel/pull/275
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabl
Hi
Thanks for helping with the docs. Keep up the work.
On Tue, Sep 23, 2014 at 10:41 AM, James Green wrote:
> Yeah that works - have updated both Transactional Client and Spring with
> notes about TransactionTemplate instead of @Transactional at the test
> method level.
>
> On 22 September 2014
GitHub user sryll opened a pull request:
https://github.com/apache/camel/pull/275
Fix logger initialization in QuartzHelper to the right class
In order to avoid misleading logentries, the logger initialization was
fixed. Also added some javadoc.
You can merge this pull request into
Yeah that works - have updated both Transactional Client and Spring with
notes about TransactionTemplate instead of @Transactional at the test
method level.
On 22 September 2014 17:42, Claus Ibsen wrote:
> Hi
>
> Thanks. I have just granted your account edit rights. Can you try if that
> works?
Thanks Christian for your response.
But my question was do we have any implication if we write too many
processor to a given request.
The way we have written our application is we have exposed a webservice and
we have number of processor in a route to process the request..
The question is more
