Hi
Have you tried the AMQ forum to see if there is a solution that works
with AMQ only?
Then we know its possible and can see if there is something needed to
be changed in camel-jms or maybe in the activemq-camel component that
is shipped with AMQ itself.
On Fri, Mar 13, 2009 at 7:39 AM, huntc
On Fri, Mar 6, 2009 at 1:46 PM, _Jens jens.riemschnei...@icw.de wrote:
Hi,
first of all, thanks to both of you, Gert and Willem, for the quick replies.
I saw that the jira was already fixed, great job.
Does this mean that the methods for disabling stream caching will be removed
in the
Hi Claus,
yes, it seems to have an effect because the lifecycle-strategy is different
when disabling JMX. The Constructor of the DefaultCamelContext uses either
DefaultLifecycleStrategy or InstrumentationLifecycleStrategy. This also has
influence on the error handling strategy.
Jens
--
View
Hi Claus,
Thanks for your reply. I forgot that I made this posting otherwise I would
have sent through an update.
I did post to the AMQ forum and then discovered for myself what the problem
was - the java client consuming the services needed authenticated access to
its keystore.
I'm going to
Here's the promised blog entry:
http://christopherhunt-software.blogspot.com/2009/03/mutual-ssl-authentication-and-ldap.html
--
View this message in context:
http://www.nabble.com/Mutual-SSL-authentication-with-Camel-applications-tp22490614p22558460.html
Sent from the Camel - Users (activemq)
The Camel team is pleased to announce the first milestone release of
the improved Apache Camel [1], version 2.0-M1.
This version features a record 368 issues fixed including:
- New examples
- New EIP: Sort
- New components: cometd, freemarker, restlet, rss
- New DataFormats: json, zip, bindy
-
