Hi, I agree that the SOAP response does look wrong. On just the element below, ns2 is declared twice (with different values), which makes for invalid SOAP, and looking at your response message ns2 was already declared on the parent element. <ns2:lineupTypeArray xmlns:ns2="" xmlns:enc=" http://www.w3.org/2001/06/soap-encoding"; xmlns:ns2=" http://gti-ia-zo.nl/ettTypes.xsd"; enc:arrayType="ns2:lineupType[0]">
I've checked your WSDL, and there's nothing obvious that would cause problems. I believe there may have been some fixes relating to namespaces applied since 1.5, so can you check if this is still a problem in the 1.6beta release? Regards, Adrian _______________________________________ Adrian Dick ([EMAIL PROTECTED]) "Roel Bindels" <[EMAIL PROTECTED]> wrote on 03/04/2006 21:22:31: > Hello listers, > > I'm having some troublems with the response message. I'm using axis > 1.5 as soap server and the Python ZSI library as a client. > There are some differences between the approach of the both > framework, but I was able to conquer those. > But now I'm getting a strange response from axis, wich I doubt to be correct. > > Can somebody please take a look at my wsdl and the response in my attachments. > > specially to the next line: > > <ns2:lineupTypeArray xmlns:ns2="" xmlns:enc=" http://www.w3. > org/2001/06/soap-encoding" xmlns:ns2=" http://gti-ia-zo.nl/ett > Types.xsd" enc:arrayType="ns2:lineupType[0]"> > > This tells me that there should be a lineupTypeArray in my wsdl > since this is pointing to ns2. I guess thet this should be an ampty > namspace and that the namspace of my wsdl should be ns3. > > Can somebody verify this or not........ > > greetings > Roel Bindels > [attachment "ett.wsdl" deleted by Adrian Dick/UK/IBM] [attachment > "getLineup.txt" deleted by Adrian Dick/UK/IBM]
