its working.
Thank you.
--
View this message in context:
http://camel.465427.n5.nabble.com/does-Camel-support-PGP-Encryption-tp5718723p5719060.html
Sent from the Camel Development mailing list archive at Nabble.com.
Yeah now it works.
Babak
--
View this message in context:
http://camel.465427.n5.nabble.com/http-central-maven-org-maven2-org-apache-cxf-cxf-rt-transports-common-2-5-5-cxf-rt-transports-commond-tp5718950p5719062.html
Sent from the Camel Development mailing list archive at Nabble.com.
Hi:
I am trying to delete the original files after backing up and encrypted.
Files are moved and ecrypted successfully. However, it fail to delete the
files:
Code:
public class FileCopierWithCamel{
public static void main(String args[]) throws Exception {
// create CamelContext
Over the weekend, I logged:
https://issues.sonatype.org/browse/MVNCENTRAL-238
and its now resolved…. Can someone in Europe double check?
Dan
On Sep 9, 2012, at 1:02 PM, Babak Vahdat wrote:
> I also get an empty content for this POM from CH.
>
> Babak
>
> Am 09.09.12 17:52 schrieb "Chris
O.K. It's fixed now on trunk.
@Claus & @Christian could you please give it another try to see how it
would work on your boxes.
Also running all the tests should now not take longer than 3 seconds
compared to around 30 seconds before (mvn clean install).
I've put the corresponding comments into th
What about a:
public interface SourceAwareExceptionHandler extends ExceptionHandler {
…add three methods….
}
Thus, no "old" code needs to change at all unless they want to use the new
methods. They would need an instanceof if they do want to use the new methods.
HOWEVER, we could also do a
On Mon, Sep 10, 2012 at 1:08 PM, Christian Schneider
wrote:
> How about adding a new ExceptionHandler interface and deprecating the old
> one. We can then allow both in Camel 2.x and remove the old one in Camel 3.
> This way we do niot introduce an incompatibility and give people some time
> to sw
How about adding a new ExceptionHandler interface and deprecating the
old one. We can then allow both in Camel 2.x and remove the old one in
Camel 3.
This way we do niot introduce an incompatibility and give people some
time to switch.
Downside is that it requires some additional code in 2.x a
Hi
See ticket, and if you got the time the nabble link
https://issues.apache.org/jira/browse/CAMEL-5587
The API on org.apache.camel.spi.ExceptionHandler has 3 methods for
handling exceptions,
CAMEL-5587 is a ticket to enhance that API with a new parameter that
has the source that called the hand
Am 10.09.12 10:52 schrieb "Babak Vahdat" unter
:
>
>
>Am 10.09.12 08:45 schrieb "Claus Ibsen" unter :
>
>>Hi
>>
>>Yep I get that failure as well running tests locally
>
>Hi
>
>Yes it fails but just randomly if you would run the tests more than just
>once. So to me there's a race condition some w
Am 10.09.12 08:45 schrieb "Claus Ibsen" unter :
>Hi
>
>Yep I get that failure as well running tests locally
Hi
Yes it fails but just randomly if you would run the tests more than just
once. So to me there's a race condition some where causing the tests to
fail from time to time. For example on
11 matches
Mail list logo
