[
https://issues.apache.org/jira/browse/SYNAPSE-895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiranya Jayathilaka updated SYNAPSE-895:
----------------------------------------
Fix Version/s: (was: FUTURE)
3.0
> Introduce a additional log to identify the issue in wrong vfs proxy
> configuration
> ---------------------------------------------------------------------------------
>
> Key: SYNAPSE-895
> URL: https://issues.apache.org/jira/browse/SYNAPSE-895
> Project: Synapse
> Issue Type: Bug
> Components: Transports
> Affects Versions: NIGHTLY
> Reporter: Vijayaratha Vijayasingam
> Assignee: Hiranya Jayathilaka
> Fix For: 3.0
>
> Attachments: vfsTransport.patch
>
>
> 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..
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
