[esb-java-user] Operation not set [sometimes] When using VFS

Ruwan Linton ruwan at wso2.com
Mon Jun 8 19:11:39 PDT 2009


Srinath Perera wrote:
> Hi All;
>
> Following code in the VFSTrasnportListener try to find the operation
> from the services.xml, and use a default value when it is not found.
> However, if the service do not have a operation whose name matches the
> default value, a operation will not be set, and consequently, the
> processing will fail at the post dispatch verifications. I guess one
> can work around by adding a parameter called "Operation" in to the
> services.xml, but IMO this is a bug.
>   
This seems to be an issue, let me dig into this a bit more and get back 
to you.

Thanks,
Ruwan
> Thanks
> Srinath
>
> AxisService service = entry.getService();
>             if (service != null) {
>                 msgContext.setAxisService(service);
>
>                 // find the operation for the message, or default to one
>                 Parameter operationParam =
> service.getParameter(BaseConstants.OPERATION_PARAM);
>                 QName operationQName = (
>                     operationParam != null ?
>
> BaseUtils.getQNameFromString(operationParam.getValue()) :
>                         BaseConstants.DEFAULT_OPERATION);
>
>                 AxisOperation operation = service.getOperation(operationQName);
>                 if (operation != null) {
>                     msgContext.setAxisOperation(operation);
>                 }
>             }
>
>   


-- 
Ruwan Linton
Senior Software Engineer & Product Manager; WSO2 ESB; http://wso2.org/esb
WSO2 Inc.; http://wso2.org
email: ruwan at wso2.com; cell: +94 77 341 3097
blog: http://ruwansblog.blogspot.com 




More information about the Esb-java-user mailing list