GitHub user zregvart opened a pull request:
https://github.com/apache/camel/pull/1782
CAMEL-11445 Declare JEE namespace in beans.xml
This adds XML namespace declaration to `beans.xml`.
@astefanutti would you mind having a look, I'm not up to date with CDI
spec, I think ther
Hi
Just a little status update, that after a bunch of different
optimisations, then the YourKit profiler is now down to showing that
the type converter registry and the uuid generator is potential
hot-spots, where the former is used a lot and we can optimise the
conversions for the core converters
The Apache Jenkins build system has built Camel.2.19.x.notest (build #64)
Status: Still Failing
Check console output at https://builds.apache.org/job/Camel.2.19.x.notest/64/
to view the results.
Hi Claus,
I already created thie JIRA ticket:
https://issues.apache.org/jira/browse/CAMEL-11438
Regards Franz
On Fri, Jun 23, 2017 at 2:21 PM, Claus Ibsen wrote:
> Hi Franz
>
> +1 this sounds good. And I agree its a good idea to separate into a
> new component.
>
> I suggest to log a JIRA ticket
Github user dmvolod closed the pull request at:
https://github.com/apache/camel/pull/1772
---
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 ena
Hi Franz
+1 this sounds good. And I agree its a good idea to separate into a
new component.
I suggest to log a JIRA ticket with 2.20 as target so we can see it on
the roadmap.
On Fri, Jun 23, 2017 at 10:10 AM, Franz Paul Forsthofer
wrote:
> Hello Claus,
>
>
>
> I want to contribute a new crypt
GitHub user onders86 opened a pull request:
https://github.com/apache/camel/pull/1781
CAMEL-11437 - probeContentType and preMove attributes causes Exchangeâ¦
â¦.FILE_CONTENT_TYPE to get dropped
This is a very specific fix for the issue.
Better solution would be pa
That was what I meant from the beginning :-)
Thanks. --Andrea Cosentino --Apache Camel PMC
MemberApache Karaf CommitterApache Servicemix PMC MemberEmail:
ancosen1985@yahoo.comTwitter: @oscerd2Github: oscerd
On Friday, June 23, 2017 11:20 AM, Franz Paul Forsth
Hello,
I have seen that all current endpoint urls do not contain the world
"camel". Therefore I will remove the world "camel" in the url. The new
endpoint urls will look as follows
crypto-cms:sign://?[options]
crypto-cms:verify://?[options]
crypto-cms:encrypt://?[options]
crypto-cms:dec
Thanks for the quick reply. O.k. I can use camel-crypto-cms as name.
Franz Forsthofer
SAP AG
On Fri, Jun 23, 2017 at 10:12 AM, Andrea Cosentino <
ancosen1...@yahoo.com.invalid> wrote:
> +1 for a new component.
>
> Maybe for the naming it can be better camel-crypto-cms, camel-cms can be
> confuse
+1 for a new component.
Maybe for the naming it can be better camel-crypto-cms, camel-cms can be
confused with a content management system. By the way it's not so important.
Nice idea and really good contribution.
Thanks Franz.
--
Andrea Cosentino
--
Apache Ca
Github user dmvolod closed the pull request at:
https://github.com/apache/camel/pull/1780
---
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 ena
Hello Claus,
I want to contribute a new crypto component which supports
encryption/decryption, signing/verifying according to the Cryptographic
Message Syntax (CMS). See the CMS specification given in
https://tools.ietf.org/html/rfc5652. This component will use the Bouncy
Castle CMS library (bcp
13 matches
Mail list logo
