[ http://issues.apache.org/jira/browse/AXIS2C-47?page=comments#action_12365390 ]
Samisa Abeysinghe commented on AXIS2C-47: ----------------------------------------- I had a look into this and it looks to me as if the currently implemented logic as it is sufficient. Those who are using the PAI should set up the message context appropriately along with the operation and call the current invoke with those msg ctx and op as parameters. > invoke_blocking/non_blocking with msg_ctx as parameter is not supported in > call.c > --------------------------------------------------------------------------------- > > Key: AXIS2C-47 > URL: http://issues.apache.org/jira/browse/AXIS2C-47 > Project: Axis2-C > Type: Bug > Versions: M0.3 > Reporter: Damitha Kumarage > Assignee: Samisa Abeysinghe > Fix For: M1.0 > > client should be able to create a soap envelope and create a message context > and set the envelope to the msg_ctx. > then he should be able to invoke > axis2_call_invoke_blocking/axis2_call_invoke_non_blocking with message context > as parameter. > But inside invoke_blocking/non_blocking the method > axis2_call_create_op_fill_flow is not called so that > request does not work properly -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
