axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eran Chinthaka (JIRA)" <>
Subject [jira] Commented: (AXIS2-235) A module should be able to add a response message within the InFlow
Date Fri, 23 Sep 2005 02:36:29 GMT
    [ ] 

Eran Chinthaka commented on AXIS2-235:

Hang on. What are you talking about here ?
In Only means In-Only. If you say in only, you can not send OUT message, except in the case
where you send a fault in the Robust In case.
Please try to identify RM scenarios separately from MEPs. And IMO, if InMessageReceiver acts
as a InOutMessageReceiver, thats is weird. If you really want that, better write your own
custom message receiver like InOptionalOutMessageReceiver.
There is no argument behind you saying AbstractInMessageReceiver is not flexible.

> A module should be able to add a response message within the InFlow
> -------------------------------------------------------------------
>          Key: AXIS2-235
>          URL:
>      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
> 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:
For more information on JIRA, see:

View raw message