[SYNAPSE-895] Introduce a additional log to identify the issue in wrong vfs proxy configuration

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: NIGHTLY
• Fix Version/s: 3.0.0
• Component/s: Transports
• Assignee: Hiranya Kasub Jayathilaka
• Reporter: Vijayaratha Vijayasingam
• Created: 27/Jul/12 10:51
• Updated: 18/Aug/13 00:09
• Resolved: 19/Jul/13 18:30

Description

When we create a vfs proxy, there is a must parameter "transport.vfs.FileURI", which we have to define.
But if user misses to define it, he gets only a warning says,

WARN -VFSTransportListener Unable to configure the service VfsToHttpProxy for the VFS transport: Service doesn't have configuration information for transport vfs. This service is being marked as faulty and will not be available over the VFS transport.

In the above warning, user could not identify what was the missing parameter..

It is better if we add a descriptive log, if that required parameter is missing in the configuration

I have added a simple patch, which basically adds a log to notify the user..