GitHub user forsthofer opened a pull request:
https://github.com/apache/camel/pull/2203
CAMEL-12181: XML Signature: '#' missing in ObjectReference attribute
of XADES element DataObjectFormat
You can merge this pull request into a Git repository by running:
$ git
GitHub user forsthofer opened a pull request:
https://github.com/apache/camel/pull/2142
CAMEL-12075: aggregator thread does not finish in iterating splitter
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/forsthofer/camel CAMEL
gest 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 crypto component which supports
> > en
?[options]
crypto-cms:decrypt://?[options]
This also means that the component name will just be "crypto-cms".
Regards Franz
SAP SE
On Fri, Jun 23, 2017 at 10:19 AM, Franz Paul Forsthofer <
emc2...@googlemail.com> wrote:
> Thanks for the quick reply. O.k. I can use camel-c
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, c
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
Hello Arpit,
if you look into the code of the component camel-crypto you find in the
class PgpKeyAccessDataFormat
sigGen.init(PGPSignature.BINARY_DOCUMENT, sigPrivateKey);
and
PGPLiteralDataGenerator litData = new PGPLiteralDataGenerator();
String fileName = findFileNa
Hello,
In https://issues.apache.org/jira/browse/CAMEL-9880 Stephan proposes an
improvement for the attachment concept in Camel.
He introduces headers for attachments. Currently an attachment is
represented in Camel by a DataHandler; in the Camel
Message you have methods like
DataHandler getAt
Hi,
try
ref:myBeanId
were myBeanId is the beran Id of a bean representing the map, for
example instance of a hash map.
Best Regards Franz
On Fri, Aug 21, 2015 at 3:14 PM, gustavo.maurizio wrote:
> Hi all.
> We are using camel with spring XML, not Java DSL.
> We need to set a header, which
gards Franz
On Mon, Jul 27, 2015 at 1:21 PM, Franz Paul Forsthofer
wrote:
> Hi Aki,
>
> there will be no change to the old behavior. Suppose you have the
> following scenario: A SOAP client sends to a CAMEL CXF consumer and
> this consumer just forwards the message to a Camel CXF p
; thanks.
> regards, aki
>
> 2015-07-21 12:44 GMT+02:00 Franz Paul Forsthofer :
>> Hi,
>>
>> can I assume that there are no objections against the patch I proposed
>> in https://issues.apache.org/jira/browse/CAMEL-8978?
>>
>> Best Regards Franz
>>
&
Hi,
can I assume that there are no objections against the patch I proposed
in https://issues.apache.org/jira/browse/CAMEL-8978?
Best Regards Franz
On Fri, Jul 17, 2015 at 10:02 AM, Franz Paul Forsthofer
wrote:
> Hi,
>
> Accessing the SOAP headers via the Cam
uot;org.apache.cxf.headers.Header.list".
For more details have a look at https://issues.apache.org/jira/browse/CAMEL-8978
Can somebody of the CXF experts comment whether my solution is
feasible. Then I will commit the patch.
Best Regards
Franz Forsthofer
Hi,
I made a suggestion to overcome some charset encoding problems in the
jsonpath component.
See https://issues.apache.org/jira/browse/CAMEL-8905.The idea is to
automatically determine the encoding if the json document has a
unicode encoding (UTF8, UTF-16LE, UTF-16BE,UTF-32BE, UTF-32LE). This
is
Hello,
i detected three different encoding problems in jsonpath. I reported
them in https://issues.apache.org/jira/browse/CAMEL-8905 and attached
also a patch.
Can somebody of you have a look at the patch? I actually can do the
commit myself. However, in this case I would like to have a reviewer.
Hi Claus and Henryk,
i provided a patch for the stream caching problem with WireTap. Please
have a look at
https://issues.apache.org/jira/browse/CAMEL-8688
Thanks and Regards Franz
Hi Claus,
I provided some time ago a solution for the above Jira task. In the
multi-cast or splitter case, cached streams are deleted by the
sub-routes so that the main route cannot access to the result of the
sub-routes. In my solution I proposed to defer the deletion of the
cached streams until
Hi,
in https://issues.apache.org/jira/browse/CAMEL-6911I make a suggestion
to improve the PGPDataFormat so that several public keys can be used
to encrypt the symmetric encryption key. Please have a look.
Regards Franz
Hi,
my account user name is 'forsthofer'
Regards Franz
On Tue, Oct 8, 2013 at 8:41 AM, Claus Ibsen wrote:
> Hi
>
> You need to create an account on wiki first. And let us know the
> account username, then we can grant you karma.
>
>
>
> On Tue, Oct 8, 2013
Hi,
I signed the ICLA and it was received by Apache. See
http://people.apache.org/committer-index.html (unlisted CLAs). There
my name is Franz Forsthofer. Can you please add me to the wiki page
editors. I want to improve the documentation for the xmlsecurity
component (XML Signature) which I
n components without
> forcing spooling to disk on end-users, without them knowing that.
>
> Fell free to log a JIRA ticket.
>
> On Wed, Sep 4, 2013 at 11:14 AM, Franz Paul Forsthofer
> wrote:
> > Hello,
> >
> > the MarschallProcessor currently returns a byte arr
Hello,
the MarschallProcessor currently returns a byte array. This does mean that
large messages are kept in memory which can lead to performance problems. I
suggest to use StreamCache instead by using CachedOutputStream instead of
ByteArrayOutputStream.
To be more concret, instead of
publi
Hi Claus,
Colm and I aggreed on the implementation please have a look at
https://issues.apache.org/jira/browse/CAMEL-6339
Will you take care that the patch will be part of 2.12.0 release?
Thanks and Regards Franz
--
View this message in context:
http://camel.465427.n5.nabble.com/XML-Signatur
t gives the data format the freedom to be used in
> > recipient lists, and other EIPs which has dynamic routing. Where as
> > data formats is static as they require to use the marshal and
> > unmarshal in the DSL.
> >
> >
> > > Babak
> > >
> > >
Hi Colm,
I made the proposal with the XML Signature component. I did not implement
it as Data Formater because I found out that the signer needs quite
different parameters than the verifier. For example, the signer needs as
input a signature algorithm, canonicalization methods, transformation
meth
Hello,
I have created a camel component for XML Signature. I created the Jira
task https://issues.apache.org/jira/browse/CAMEL-6339. Please have a
look at it and let me know whether you will add this to the camel
distribution.
Regards Franz
ty component from Camel?
> Maybe that's the place where it fits the best?
>
> I suggest to take a second look
>
>
> On Tue, Mar 12, 2013 at 7:33 AM, Franz Paul Forsthofer
> wrote:
>> Hello,
>>
>> I want to contribute a new component for XML Digital Signat
Hello,
I want to contribute a new component for XML Digital Signature. There
shall be two endpoints; the signer endpoint shall sign the body of the
in-message and create an XML digital signature in the out-message, the
verifier endpoint shall verify the XML signature contained in the body
of the i
28 matches
Mail list logo
