Hi Darran,
this seems to be a bug. I cannot find this requirement in any of the
specs either. If this really needs to get fixed please create a jira
issue for it.
cheers
-thomas
On Thu, 2007-10-18 at 16:49 +0100, Darran Lofthouse wrote:
Would it be possible for one of you to take a look at this case
please?
https://na1.salesforce.com/50030000003j9iM
The customer is making a DII call to a RPC endpoint and in the response
the first child element of the soap body is 'retrievePackagesResponse'
however we are assuming it is called 'result'.
I have had a look at the 'org.jboss.ws.core.CommonSOAPBinding'
implementation and I can see that if this was a Document endpoint it
would have been able to fall back to checking by type but as it is RPC
it is skipping this and throwing the following error: -
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:536)
at org.jboss.ws.core.jaxrpc.client.CallImpl.invoke(CallImpl.java:277)
at com.hrlogix.view.test.WebService.main(WebService.java:54)
Caused by: org.jboss.ws.WSException: Cannot find child element: result
at
org.jboss.ws.core.CommonSOAPBinding.getParameterFromMessage(CommonSOAPBinding.java:906)
at
org.jboss.ws.core.CommonSOAPBinding.unbindResponseMessage(CommonSOAPBinding.java:622)
at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:365)
>From looking at the code I can not see any way that the name of the
return parameter can be set. Is this something that should be possible?
I am unaware of a requirement for the result to be contained within an
element called 'result'.
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx