You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Chamikara Jayalath (JIRA)" <ji...@apache.org> on 2005/09/22 11:58:28 UTC

[jira] Created: (AXIS2-235) A module should be able to add a response message within the InFlow

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


[jira] Resolved: (AXIS2-235) A module should be able to add a response message within the InFlow

Posted by "Chamikara Jayalath (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/AXIS2-235?page=all ]
     
Chamikara Jayalath resolved AXIS2-235:
--------------------------------------

    Resolution: Fixed

< see my last comment >

> 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


[jira] Commented: (AXIS2-235) A module should be able to add a response message within the InFlow

Posted by "Eran Chinthaka (JIRA)" <ji...@apache.org>.
    [ http://issues.apache.org/jira/browse/AXIS2-235?page=comments#action_12331089 ] 

Eran Chinthaka commented on AXIS2-235:
--------------------------------------

Can the RM IN handler itself send the ack, without asking the message receiver to send it, without making the existing MEP much more complex ?. I'm definitely -1 if default INOnlyMessageReceiver tries to send a response. 
IMO, that is the best way to do it. If that helps, can you please resolve this issue also.

> 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


[jira] Commented: (AXIS2-235) A module should be able to add a response message within the InFlow

Posted by "Chamikara Jayalath (JIRA)" <ji...@apache.org>.
    [ http://issues.apache.org/jira/browse/AXIS2-235?page=comments#action_12330252 ] 

Chamikara Jayalath commented on AXIS2-235:
------------------------------------------

Ya. It obviously can be done with a new message receiver. But only the RMModules knows about this behaviour. So when engaging the RMModule the user has to go through the operations of his Service and change the MessageReceivers accordingly. Well, this can also be justified. He had to do some work before adding the RMModule. He has to read the documentation that comes with the RMModule and change the MessageReceiver for InOnly operations. But what if another module want him to apply some other MessageReceiver for these operations.

Thats why I tried to do it without changing the MessageReceiver.

But if there is no other way. Well go for that  :(


Chamikara

> 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


[jira] Commented: (AXIS2-235) A module should be able to add a response message within the InFlow

Posted by "Chamikara Jayalath (JIRA)" <ji...@apache.org>.
    [ 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


[jira] Commented: (AXIS2-235) A module should be able to add a response message within the InFlow

Posted by "Eran Chinthaka (JIRA)" <ji...@apache.org>.
    [ http://issues.apache.org/jira/browse/AXIS2-235?page=comments#action_12330249 ] 

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: 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