AbstractFileGateway setFileWorking is destroying the exception information instead of showing it. ------------------------------------------------------------------------------------------------- Key: JBESB-3702 URL: https://issues.jboss.org/browse/JBESB-3702 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.10, 4.9 Reporter: Fabricio González I was having some troubles while configuring an FTP listener and found out that the method setFileWorking in the class AbstractFileGateway is currently destroying the exception information and instead it only shows a standard message without telling us what was the original exception (Also, the message that it shows is wrong because it shows file.getAbsolutePath() and that shows a wrong path when working with FTP files, but this is not the main bug). Several classes down the path of the rename that setFileWorking is trying to do, add their custom information to the GatewayException that they throw so that developers can know what is falling. But setFileWorking is not displaying that information. I think that there should be an option to add that info if we want to see while developing, at least add a log.debug with the original exception. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira