I was able to successfully return a native array using the SOAP provider. I guess it is understandable that the SOAP provider would not like Java types like Collection.
Thanks for your help, Ron ________________________________ From: Aleksander Slominski [mailto:[EMAIL PROTECTED] Sent: Tue 10/5/2004 11:29 AM To: [EMAIL PROTECTED] Subject: Re: WSIF alive ? Ron Ridenour wrote: >Heres a little activity. >Any help would be appreciated. > >I am having a problem when returning a java.util.Collection from a method invocation. > >I am using WASD Integration Edition v 5.1 >I create a WSIFStub as follows: > Context initialContext = new InitialContext(); > WSIFServiceStubRef stubRef = new WSIFServiceStubRef > (wsdlLoc,serviceNamespace,serviceName,portTypeNamespace,portTypeName,preferedPortName,interfaceClass.getName()); > JndiHelper.recursiveBind(new InitialContext(), interfaceClass.getName(), stubRef); > return initialContext.lookup(interfaceClass.getName()); > >The WSDL method declares that the return type is an array of AnyType. >The actual returned type is Arraylist >This is a SOAP call and the actual call object does indeed have the array >values after the method invocation but the returned object from the stub >is null. > >Aleksander, do you have any ideas about this? > >Has anybody been able to return a collection or an array from the >remote method and is array of AnyType the correct WSDL binding. > > if you are using Apache AXIS SOAP provider then this would be the problem in AXIS - i do not think axis supports collection and it prefers arrays ... can you change interface to return an array and give it try? alek -- The best way to predict the future is to invent it - Alan Kay
