Many thanks Franz, that's what I've implemented yesterday and I was going to
come back here to update the post and you beat me.
--
View this message in context:
http://camel.465427.n5.nabble.com/XMLSecurity-not-generating-tp5798321p5798419.html
Sent from the Camel - Users mailing list
Thanks for your reply. My query is around Camel XML security component. I
wanted to know if it is possible to generate the *X509Certificate* element
in the *Signature* element - see below example.
Of course I can use Java API/Bouncycastle to generate, but that's last
resort.
Hi
I am using Camel XML security component to sign an xml using the following
setup:
Hi James
Unfortunately, the current implementation of Camel Schemaron only supports
classpath and filesystem location for the rules. Create A Jira ticket and I
am sure someone would look at.
Thanks
--
View this message in context:
Hi
Recently we started using MDCSiftingAppender to push logs into syslog and
we've noticed leaked UDP ports - see config set below. Here is a little bit
of context, we deploy around 20 bundles into apache Karaf and in one
occasion we've noticed around 26 thousands ports for syslog appender and
Hi Willem
Thanks for your prompt response. The support for hazelcastInstance is on
camel 2.14 I didn't realise that. I will explore that further. You mentioned
I may need to expose the instance as a service, can you show me an example?
the documentation doesn't sow that.
Thanks
--
View this
I haven't solved this issue yet, but I have got a workaround which I would
like to share with you here.
By adding the failover protocol to the borkerUrl see below, the failover
protocol seems to handle connection failure well.
activemq.brokerURL=failover:(nio://activemq:61616) instead of simply
