axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Deepal Jayasinghe (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (AXIS2-1349) RPCMessageReceiver misbehaviour
Date Fri, 20 Oct 2006 06:50:37 GMT
     [ http://issues.apache.org/jira/browse/AXIS2-1349?page=all ]

Deepal Jayasinghe resolved AXIS2-1349.
--------------------------------------

    Resolution: Incomplete

If you have void method , then you should not use RPCMessageReceiver since your map is in-only.
So better to use RPCInonlyMR.

> RPCMessageReceiver misbehaviour
> -------------------------------
>
>                 Key: AXIS2-1349
>                 URL: http://issues.apache.org/jira/browse/AXIS2-1349
>             Project: Apache Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: rpc
>    Affects Versions: 1.1
>            Reporter: Ruwan Linton
>         Assigned To: Deepal Jayasinghe
>
> I have writen a void setName operation and engaged the RPCMessageReceiver in the services.xml
> When I tried to invoke this method using fireAndForget it worked but when I tried to
do sendRecieve Axis2 engine gave me an AxisFault
> org.apache.axis2.AxisFault: Exception occurred while trying to invoke service method
setName
> 	at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:294)
> 	at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:569)
> 	at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:500)
> 	at org.apache.axis2.messageReciever.test.client.Axis2TestathonClient.main(Axis2TestathonClient.java:38)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at com.intellij.rt.execution.application.AppMain.main(AppMain.java:90)
> This is because a npe is occured in the RPCMessageReceiver because it is trying to get
some parameters from the outaxisMessage without checking weather it is null or not.
> I think Axis engine should not fail at this point.
> <<Code from the RPCMessageReceiver
>      
> L: 130           // Handling the response
> L: 131           AxisMessage outaxisMessage = op.getMessage(WSDLConstants.MESSAGE_LABEL_OUT_VALUE);
> L: 132           if (inAxisMessage != null) {
> L: 134               messageNameSpace = outaxisMessage.getElementQName().getNamespaceURI();
> L: 135           }
> >>

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

        

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org


Mime
View raw message