Hello,
in
https://github.com/apache/camel/tree/main/dsl/camel-xml-io-dsl/src/test/resources/org/apache/camel/dsl/xml/io,
I found examples for the XML Io DSL. I did not see any example where a
bean references another, something like the following
Or where a bean referenc
Hello,
sometimes the native build runs longer than the timeout of 10 minutes.
Is it possible to configure the timeout contained in the Kubernetes
Build resource?
spec:
configuration: {}
tasks:
...
timeout: 10m0s
Regards Franz
Hello,
>From https://camel.apache.org/camel-k/2.0.x/architecture/cr/camel-catalog.html
I understood that the Camel K Operator uses the CamelCatalog to
determine the dependencies of the Camel route. Then the Camel K
Operator uses these dependencies in a Maven build to assembly the
transitive depend
Hello Ayache,
you can do this by implementing your own KeyAccessor. The KeyAccessor
interface
https://github.com/apache/camel/blob/master/components/camel-xmlsecurity/src/main/java/org/apache/camel/component/xmlsecurity/api/KeyAccessor.java
contains the method
KeyInfo getKeyInfo(Message message,
Hello Niklas,
can you point me in the spec https://www.w3.org/TR/xmldsig-core/ to the
part which allows to define transformations also for the KeyInfo element. I
could not find such kind of definition. If it is there in the specification
we might think about to include this into our camel processo
Hi Ronald,
Try to switch on stream caching. see http://camel.apache.org/stream-caching.html
Best Regards Franz
On Tue, Jun 28, 2016 at 4:35 PM, OzzO wrote:
> Hi,
>
> I have created a proxy service in Camel to accept an incoming request and
> send a copy of the message (clone) to a number of rec
Hi Jack,
the XML Signature component does not support the KeyInfo content you
need. But what you could do is that you create the KeyInfo element on
your own before you call the XML Signature component.
Then I think it is better to use enveloped Signature than the detached
Signature mode. You have
Hi Kalyan,
this issue is known. See
https://issues.apache.org/jira/browse/CAMEL-8419 . CAMEL-8419 contains
even a patch. But this patch is more a workaround, therefore this
patch was never merged.
Best Regards Franz
On Wed, Dec 16, 2015 at 12:35 PM, calyan.bandi wrote:
> Hi,
>
> I found the anw
Hi Hubertus,
the Stream Caches and their corresponding files are closed/deleted at
the end of the route, because it could be that some processor in the
route still needs the stream. Maybe it helps in your case to increase
the threshold so that only the first big file 400 MB is written into
the fil
Hi,
from the camel message you can get the exchange and from the exchange
the camel context
message.getExchange().getContext().
Regards Franz
On Tue, Aug 11, 2015 at 5:54 PM, akoufoudakis wrote:
> Dear all!
>
> I know that one can lookup for an OSGi service the following way:
> Runnable r = (R
Hi Shashank,
have a look at the direct_vm component: http://camel.apache.org/direct-vm.html.
Maybe you can use this component in combination with recipient list
(https://camel.apache.org/recipient-list.html) where you dynamically
can set the receiver URIs.
Regards Franz
On Fri, Jul 10, 2015 at 1
Hello Lakshmi,
it could be that this issue is related to
https://issues.apache.org/jira/browse/CAMEL-8688
There we have made a patch in the current snapshot (version 2.16)
Can you try to reproduce your problem on the current snapshot?
Regards Franz
On Tue, May 12, 2015 at 11:39 AM, lakshmi.pra
the cached body.
>>
>> Franz, would you be so kind and create a pull request with your fix?
>> Somebody will review it and merge. Thanks in advance!
>>
>> Cheers!
>>
>> wt., 21.04.2015 o 16:25 użytkownik Franz Paul Forsthofer <
a bug or
> does it work as designed?
> Can we use a workaround to avoid this behaviour, for example by not
> deleting the temp files?
>
>
> Kind regards,
>
> Geert
>
> On Tue, Apr 21, 2015 at 10:37 AM, Franz Paul Forsthofer <
> emc2...@googlemail.com> wrote:
Hello Geert,
there is no solution yet for your problem. Currently the stream cache
file is removed at the end of the route which created the file. In
your case the stream cache file is deleted when the "direct:start"
route is finished. The wire tap runs in a separate thread and
therefore it can ha
Hello Lakshmi and Stephan,
I created the bug https://issues.apache.org/jira/browse/CAMEL-8284
It does contain a solution proposal. Please have a look.
Regards Franz
On Fri, Jan 16, 2015 at 8:46 AM, lakshmi.prashant
wrote:
> Hi Stephan,
>
>The body of the main exchange should be copied to t
Hello Shail,
please try camel stream caching. See http://camel.apache.org/stream-caching.html
Regards Franz
On Fri, Nov 21, 2014 at 8:28 PM, Shail wrote:
> Hi,
>
> I'm using camel ver 2.14.0 in our application. We download the file from
> sftp server and then process it. The file is pgp encrypt
Hello Shail,
can you please provide the stack trace of the exception and the exact
exception message.
Regards Franz
On Fri, Nov 21, 2014 at 8:45 PM, Shail wrote:
> Hi,
>
> I'm using camel ver 2.14.0. I'm successfully able to decrypt a file using
> pgp() function when I encrypt a csv file using
Hello Gonzalo Vàsquez,
KeyValue: PublicKey key = cert.getPublicKey();
KeyValue keyInfoFactory.newKeyValue(key);
List keyInfoContent = new ArrayList(1));
if (keyValue != null) {
keyInfoContent.add(keyValue);
}
KeyInfo keyInfo = keyInfoF
HI Charles and Gonzalo,
I do not think it is necessary to develop a new dataformat. There is
already the component xmlsecurity ( see
http://camel.apache.org/xml-security-component.html ) which supports
XML Signature. XaDES-BES (http://www.w3.org/TR/XAdES/) just adds
additional XML elements to the
Hello,
I have a very simple example which shows that the problem does not
only occur for MultiCast. The problem always occurs when in a
sub-route the message body is streamed via CachedOutputStream to the
file system and the cached file is deleted at the end of the
soub-route, although the main-ro
Hi,
then you should try to find out how the DOMSource is transformed to
String. I guess it is transfomed first to a Stream and then to String.
In this case you need the correct encoding.
Regards Franz
On Thu, Jul 24, 2014 at 2:02 PM, vdhawan wrote:
> Thanks for response Franz.
>
> Bean returns
Hi,
what format does return the bean, if it is a byte array or stream then
you have to specify the encoding in the
step:
Regards Franz
On Thu, Jul 24, 2014 at 12:17 PM, vdhawan wrote:
> Hello,
>
> In my camel context, i invoke a java bean (which does some processing) and
> returns the body in
Hi,
this is a known issue see
https://issues.apache.org/jira/browse/CAMEL-7055 and is fixed in
2.12.3
Regards Franz
On Thu, Feb 13, 2014 at 5:03 AM, Rural Hunter wrote:
> Hi,
>
> I'm using Camel 2.12.2 and enabled stream caching with this code:
> context.setStreamCaching(true);
>
> Sometimes I
Hi Hassan,
I also tested the route with the direct endpoint. It also worked in
the snapshot version.
Regards Franz
On Fri, Jan 17, 2014 at 11:07 AM, hshicx wrote:
> Hi,
>
> To be more precise in my example for Issue 1, I am using a "direct:" between
> the file producer and the PGP decryption:
>
Hi,
I also tested the Issue 1 in the current snapshot version. There it
did not occur.
Regards Franz
On Thu, Jan 16, 2014 at 8:19 PM, hshicx wrote:
> Hi,
>
> I have identified two possible issues with the decryption using PGPFormat
> or with the way I have been using it.
>
> *Issue 1:*
> PGPFo
ello,
does the class com.airtel.money.camel_xmlsecurity.api.DefaultKeyAccessor
implement the interface
org.apache.camel.component.xmlsecurity.api.KeyAccessor? I am asking because
the bean used in the parameter 'keyAccessor' of the xmlsecurity component
must be of type org.apache.camel.component.xm
Hi Rafal,
please try handled(false);
My understanding is that then the error handler is called. However, I do
not understand why the first example with handled(true) works.
Regards Franz Forsthofer
--
SAP AG
e-mail: franz.forstho...@sap.com
On Tue, May 14, 2013 at 10:53
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
29 matches
Mail list logo