[jbossws-issues] [JBoss JIRA] Updated: (JBWS-1862) RPC DII Calls Assume response parameter is called 'result' in the response message.

Darran Lofthouse (JIRA) jira-events at lists.jboss.org
Tue Oct 23 06:58:01 EDT 2007


     [ http://jira.jboss.com/jira/browse/JBWS-1862?page=all ]

Darran Lofthouse updated JBWS-1862:
-----------------------------------

        Summary: RPC DII Calls Assume response parameter is called 'result' in the response message.  (was: RPC DII Calls Assume child element of soap:body is called 'result' in the response message.)
    Description: 
RPC DII Calls Assume response parameter is called 'result' in the response message.

For document style endpoints it will fall back to checking the type but for RPC calls if the name does not match the following error will be reported.

java.rmi.RemoteException: Call invocation failed; nested exception is: 
	org.jboss.ws.WSException: Cannot find child element: result
	at org.jboss.ws.core.jaxrpc.client.CallImpl.invokeInternal(CallImpl.java:526)
	at org.jboss.ws.core.jaxrpc.client.CallImpl.invoke(CallImpl.java:276)
        ...
Caused by: org.jboss.ws.WSException: Cannot find child element: result
	at org.jboss.ws.core.CommonSOAPBinding.getParameterFromMessage(CommonSOAPBinding.java:866)
	at org.jboss.ws.core.CommonSOAPBinding.unbindResponseMessage(CommonSOAPBinding.java:586)
	at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:356)
	at org.jboss.ws.core.jaxrpc.client.CallImpl.invokeInternal(CallImpl.java:507)
	... 2 more

This is caused with the following response message: -

<env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/'>
 <env:Header/>
 <env:Body>
  <ns1:echoResponse xmlns:ns1='http://org.jboss.test.ws/jbws1862'>
   <String_2>Hello World!!</String_2>
  </ns1:echoResponse>
 </env:Body>
</env:Envelope>

Here the issue is that the 'String_2' element is not called 'result'.



  was:
RPC DII Calls Assume child element of soap:body is called 'result' in the response message.

For document style endpoints it will fall back to checking the type but for RPC calls if the name does not match the following error will be reported.

java.rmi.RemoteException: Call invocation failed; nested exception is: 
	org.jboss.ws.WSException: Cannot find child element: result
	at org.jboss.ws.core.jaxrpc.client.CallImpl.invokeInternal(CallImpl.java:526)
	at org.jboss.ws.core.jaxrpc.client.CallImpl.invoke(CallImpl.java:276)
        ...
Caused by: org.jboss.ws.WSException: Cannot find child element: result
	at org.jboss.ws.core.CommonSOAPBinding.getParameterFromMessage(CommonSOAPBinding.java:866)
	at org.jboss.ws.core.CommonSOAPBinding.unbindResponseMessage(CommonSOAPBinding.java:586)
	at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:356)
	at org.jboss.ws.core.jaxrpc.client.CallImpl.invokeInternal(CallImpl.java:507)
	... 2 more




> RPC DII Calls Assume response parameter is called 'result' in the response message.
> -----------------------------------------------------------------------------------
>
>                 Key: JBWS-1862
>                 URL: http://jira.jboss.com/jira/browse/JBWS-1862
>             Project: JBoss Web Services
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: jbossws-jaxrpc
>    Affects Versions: jbossws-1.2.1
>            Reporter: Darran Lofthouse
>         Assigned To: Darran Lofthouse
>             Fix For:  jbossws-2.0.3
>
>
> RPC DII Calls Assume response parameter is called 'result' in the response message.
> For document style endpoints it will fall back to checking the type but for RPC calls if the name does not match the following error will be reported.
> java.rmi.RemoteException: Call invocation failed; nested exception is: 
> 	org.jboss.ws.WSException: Cannot find child element: result
> 	at org.jboss.ws.core.jaxrpc.client.CallImpl.invokeInternal(CallImpl.java:526)
> 	at org.jboss.ws.core.jaxrpc.client.CallImpl.invoke(CallImpl.java:276)
>         ...
> Caused by: org.jboss.ws.WSException: Cannot find child element: result
> 	at org.jboss.ws.core.CommonSOAPBinding.getParameterFromMessage(CommonSOAPBinding.java:866)
> 	at org.jboss.ws.core.CommonSOAPBinding.unbindResponseMessage(CommonSOAPBinding.java:586)
> 	at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:356)
> 	at org.jboss.ws.core.jaxrpc.client.CallImpl.invokeInternal(CallImpl.java:507)
> 	... 2 more
> This is caused with the following response message: -
> <env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/'>
>  <env:Header/>
>  <env:Body>
>   <ns1:echoResponse xmlns:ns1='http://org.jboss.test.ws/jbws1862'>
>    <String_2>Hello World!!</String_2>
>   </ns1:echoResponse>
>  </env:Body>
> </env:Envelope>
> Here the issue is that the 'String_2' element is not called 'result'.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the jbossws-issues mailing list