Enhancing the exception logging will help developer in such cases.
" If detailed message is not provided by the exception, name of the exception
should be printed in logs " .
In this case FailedToCreateRouteException should check if cause.getMessage() is
not null. In case it is null,
name of exception can be passed so that developer knows what is causing the
issue.
//
public FailedToCreateRouteException(String routeId, String route, String at,
Throwable cause) {
super("Failed to create route " + routeId + " at: >>> " + at + " <<< in
route: " + getRouteMessage(route) + " because of " + cause.getMessage(), cause);
this.routeId = routeId;
}
________________________________________
From: Claus Ibsen [claus.ib...@gmail.com]
Sent: Thursday, July 24, 2014 6:44 PM
To: users@camel.apache.org
Subject: Re: Problem encrypting the password using Camel Jasypt component
Hi
There is also this ticket, maybe related to your issue
https://issues.apache.org/jira/browse/CAMEL-7630
On Thu, Jul 24, 2014 at 3:07 PM, arvind <arvindpradha...@gmail.com> wrote:
> Thanks for your great help Ravi. I have regenerated the encrypted password
> using the master password and reading it from properties file but still the
> issue persists.
>
> Logs shows PropertiesComponent class parsing uri and properties but don't
> see JasyptPropertiesParser
> does any activity even if it is mentioned in the xml as in the below link
>
> http://camel.apache.org/jasypt.html
>
>
>
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Problem-encrypting-the-password-using-Camel-Jasypt-component-tp5753644p5754385.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibsen
-----------------
Red Hat, Inc.
Email: cib...@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
hawtio: http://hawt.io/
fabric8: http://fabric8.io/
This e-mail and any files transmitted with it are for the sole use of the
intended recipient(s) and may contain confidential and privileged information.
If you are not the intended recipient(s), please reply to the sender and
destroy all copies of the original message. Any unauthorized review, use,
disclosure, dissemination, forwarding, printing or copying of this email,
and/or any action taken in reliance on the contents of this e-mail is strictly
prohibited and may be unlawful. Where permitted by applicable law, this e-mail
and other e-mail communications sent to and from Cognizant e-mail addresses may
be monitored.
