[ http://issues.apache.org/jira/browse/AXIS2-235?page=comments#action_12331090 ]
Chamikara Jayalath commented on AXIS2-235: ------------------------------------------ Thats how we are currently doing it. It has just one problem. If the MessageReceiver is RobustInOnly, and a fault get thrown there will be no way to send the fault (if the FaultTo is anonymous). Since this seems to be a rare case lets bear with it and close the issue :( But I would love to see a meshanism that allows a module to do something after the invocation of an InOnly request. I am -1 for doing this by replacing the MessageReceiver since the service has nothing to do with it (This is a module specific task like sending an ack) > A module should be able to add a response message within the InFlow > ------------------------------------------------------------------- > > Key: AXIS2-235 > URL: http://issues.apache.org/jira/browse/AXIS2-235 > Project: Apache Axis 2.0 (Axis2) > Type: New Feature > Reporter: Chamikara Jayalath > > Suppose the user has deployed a Ping Service (with a one-way ping operation) > and RM module is deployed. Only the RMHandlers of the in path get called > (since the user has set an InOnly message receiver). The RM module may want > to send an acknowledgement message as response instead of simply sending 202. > So the RMHandlers of the InFlow should be able to set this message beforehand. > One way to do this is making AbstractInMessageReceiver more flexible. If a > response message has been set in the OperationContext (by a handler in the > InFlow) the AbstractInMessageReceiver has to work as an InOut message > receiver and it should send this message. > Or is there a better way? -- 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
