On 21/01/2011 11:07, Mike Edwards wrote:
On 20/01/2011 23:29, ant elder wrote:
On Thu, Jan 20, 2011 at 9:36 PM, Scott Kurz<[email protected]> wrote:
I just committed what I hope is a fix in r1061531.

It made the copyInput IndexOutOfBoundsException in
sample-implementation-extension go away... (will give some more
thought to whether this fix to interface-wsdl is the best solution).

I can't run that async-services test yet.. I need to update my mvn
repo.. but I'm pretty confident my fix should work for that as well.

That said..clearly my testing wasn't good enough if Mike's seeing
failures all over the place.. so I'm doing some more careful testing
now.

Scott


Thats fixed all the IndexOutOfBoundsException for me. I do still get
other test fails in
testing\itest\ws\holder-ws-service-multiple-outputs and
testing\itest\async-services

...ant

Folks,

I think I have a fix for the async-services failures:

for an interface with the async server format, the databinding applied to the 
response parameter was
being set to IDL:INPUT when it should be IDL:OUTPUT - this is in 
JavaInterfaceImpl.

Changing this enables the async-services Itests to all pass.

The holder-ws-service-multiple-outputs is a different problem I suspect.

Note: Fixing this raises the question of whether async server interfaces can 
have holders - and I
think the answer is "NO". I'll discuss that point separately on the list.

Yours, Mike.



Fix committed at 1061775

Yours,  Mike.

Reply via email to