[jbossws-dev] Re: DII Implementation

[Darran Lofthouse]

Sorry my original description was slightly wrong, it is not the child of
soap:body that we expect to be called 'result' but the name of the
return parameter. 

I have created a Jira issue and put together a test case to demonstrate
the failure: -

http://jira.jboss.com/jira/browse/JBWS-1862

The Jira issue shows the response message being received by the client.

The test case I am testing this with is here: -

http://anonsvn.jboss.org/repos/jbossws/stack/native/branches/dlofthouse/JBWS-1862/src/test/java/org/jboss/test/ws/jaxrpc/jbws1862/JBWS1862TestCase.java

[I don't expect all of these approaches to work but I wanted to test a
couple of different ways of performing the call.]

The methods 'testUnconfiguredCall()', 'testConfiguredCall()' and
'testPartlyConfiguredCall()' are all failing with the 'Cannot find child
element: result' error shown in the Jira issue.

In my test case I have also created the method
'testUnconfiguredCall_2()' to try and set the name of the return
parameter but that is failing with the error: -

java.lang.ArrayIndexOutOfBoundsException: 1
	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
org.jboss.test.ws.jaxrpc.jbws1862.JBWS1862TestCase.testUnconfiguredCall_2(JBWS1862TestCase.java:92)

This is because the OUT param is being incorrectly processed as an IN
param.

I have been through the specifications but I am unable to find
conclusive information on how the Call interface should be used and
looking at the specifications some  of this may even be stack specific.

Would it be possible for one of you to have a look at my test case and
let me know which (if any) of the test scenarios we should actually
support.  

The customer has been trying to use the approach in
'testUnconfiguredCall()' as that is what they were using in the code
they are porting but they are flexible to make alterations.

-- 

Regards,
Darran Lofthouse.

Senior Software Maintenance Engineer
JBoss, a division of Red Hat


On Mon, 2007-10-22 at 10:12 +0200, Thomas Diesler wrote:
> 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'.
> >