[
https://wso2.org/jira/browse/COMMONS-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Charitha Kankanamge closed COMMONS-57.
--------------------------------------
Verified and closed the bug
> Mercury:Server responds with 202 and client gets AxisFault when an RM enabled
> service is invoked without engaging Mercury at the client side
> --------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: COMMONS-57
> URL: https://wso2.org/jira/browse/COMMONS-57
> Project: WSO2 Commons
> Issue Type: Bug
> Components: Mercury
> Environment: winxp, jdk15
> Reporter: Charitha Kankanamge
> Assignee: Amila Suriarachchi
>
> As far as I can remember, sandesha2 engaged service can be invoked by a
> client which does not know anything about RM. In other words, client can
> control reliable messaging simply by engaging and disengaging sandesha in
> client side.
> However, In Mercury implementation, if mercury is engaged at the service, it
> is essential for client to be RM aware. If client tries to simply invoke an
> mercury engaged service, server responds with 202 Accepted message. Also,
> client gets an AxisFault.
> org.apache.axis2.AxisFault: The input stream for an incoming message is null.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://wso2.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Esb-java-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev
