Hi All, I have notified that Sandesha2 module cant be engaged in the way which was described in [1]<http://wso2.org/project/app-server/4.1.2/docs/commodity_quote_guide.html>. In the client side it shows the follwoing error,
ERROR [2012-06-21 12:19:47,991] The endpoint reference (EPR) for the Operation not found is and the WSA Action = . If this EPR was previously reachable, please contact the server administrator. When I did a SOAP tracing in AS, I found that the Addressing module is not engaged properly in the response SOAP message. That causes the Sandesha2 handshaking protocol to crash by not having necessary EPRs. The following SOAP message is the SOAP message which was returned to the first handshaking SOAP message, and it doesn't have addressing headers. <soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope";> <soapenv:Header /> <soapenv:Body> <ns:greetResponse xmlns:ns="http://www.wso2.org/types";> <return>Hello World, AndunSLG !!!</return> </ns:greetResponse> </soapenv:Body> </soapenv:Envelope> In the org.apache.axiom.soap.impl.llom.SOAPHeaderImpl class's 127 line has the following Boolean check which have to return true for the correct excution, return (rolePlayer == null || rolePlayer.isUltimateDestination()); But in the current carbon trunk, the rolePlayer object is a instance of org.wso2.carbon.stratos.deployment.SuperTenantRolePlayer. It has the method isUltimateDestination() implemented as follows, public boolean isUltimateDestination() { return false; } So because of that Axis2's org.apache.axis2.handlers.addressing.AddressingInHandler class disables the AddressignOutHandler. So no addressing happens at the out flow. That causes all the trouble in Addressing and Sandesha2. I put return true experimentally and that makes all the troubles back to normal. So is the implementation of public boolean isUltimateDestination() is correct ?
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
