Mitko, Retested and all of the simpleDocLit operations pass. Cool! Are you going to do the complexDocLit too?
Yes, I agree that the prefixes do NOT have to be the same. Our test validation is just a bit primitive. By the way, you can download Apache Axis and use it for your own testing of the group H and group I client/server. You should download a recent (17 Nov 2002 or later) version of the source tree, building it, then go to the java/test/wsdl/interop4/* directories to build and run the test clients. To run test Axis test clients, execute 'run.sh' (or the java command it contains) with the endpoint (not WSDL) of the test service. http://xml.apache.org/axis - Click on the "CVS Repository" link for anonymous CVS instructions. For some reason the nightly builds have stopped running, so there isn't a binary kit available. For SoapBuilders that would like to test against an Axis group H/I endpoint on their own (until we can get an endpoint up on nagoya) 1. Build axis: 'ant clean all-tests' from the top level 'java' directory 2. Set the CLASSPATH to point at the directory java/build/classes 3. execute: java org.apache.axis.transport.http.SimpleAxisServer 4. Deploy the test services by running java org.apache.axis.client.AdminClient <path>/deploy.wsdd Where <path> is one of java/build/work/test/wsdl/interop4/{groupH,groupi}/* 5. Access the list of deployed services/WSDL at http://localhost:8080/axis/services/ -- Tom Jordahl Macromedia Server Development -----Original Message----- From: Mitko Iliev [mailto:imitko@;techno-link.com] Sent: Thursday, November 07, 2002 5:03 AM To: [EMAIL PROTECTED] Cc: '[EMAIL PROTECTED]' Subject: Re: [soapbuilders] experimental endpoints from group H, I Hi, The echoAnyElement and RetAny do parse of the incoming XML fragment to ensure at least well formed XML, so the product of parsing is serialized on output. Anyway IMHO the Namespace prefixes are not mandatory to be the same, right ? The rest of failures re:simpleDocLit are fixed now, could you verify please? Thanks a lot, Mitko Tom Jordahl wrote: > I ran the Apache Axis client tests (test/wsdl/interop4) against these endpoints > (after fixing a minor bug in our test driver to correctly use a provided URL). > > Results: > > simpleRpcEnc: All pass > > complexRpcEnc: All Pass > > Group I - XSD tests - all pass except: > There was 1 failure: > 1) test22Round4XSDTestSoapRetAny(test.wsdl.interop4.groupi.Round4XSDTestTestCase) > expected:<<n0:world xmlns:n0="hello"/>> > but was:<<ns1:world xmlns:ns1="hello"/>> > > Which I believe is just an artifact of the "toString" validation in our test. > > > simpleDocLit: 4 failures > > 1. echoMultipleFaults3 > When passed a 'whichFault' value of "2", still returns a <StringPart> element >instead of a <String2Part> element: > > ==Request=============================== > <?xml version="1.0" encoding="UTF-8"?> > <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; >xmlns:xsd="http://www.w3.org/2001/XMLSchema"; >xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> > <soapenv:Body> > <echoMultipleFaults3Request >xmlns="http://soapinterop.org/types/requestresponse";> > <whichFault xmlns="">2</whichFault> > <param1 xmlns="">Param1</param1> > <param2 xmlns="">Param2</param2> > </echoMultipleFaults3Request> > </soapenv:Body> > </soapenv:Envelope> > ==Response================================ > <?xml version='1.0'?> > <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"; >xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"; >xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; >xmlns:xsd="http://www.w3.org/2001/XMLSchema"; >xmlns:dt="urn:schemas-microsoft-com:datatypes" >xmlns:ds="http://www.w3.org/2000/09/xmldsig#"; >xmlns:xenc="http://www.w3.org/2001/04/xmlenc#"; >xmlns:wsse="http://schemas.xmlsoap.org/ws/2002/07/secext"; >xmlns:ref="http://schemas.xmlsoap.org/ws/2002/04/reference/"; >xmlns:ns1="http://soapinterop.org/types/part"; >xmlns:ns0="http://soapinterop.org/types/requestresponse"xmlns:wsdl='services.wsdl' > > <SOAP:Body> > <SOAP:Fault> > <faultcode>SOAP:Server</faultcode> > <faultstring>[Virtuoso SOAP server] echoMultipleFaults3</faultstring> > <detail> > <ns1:StringPart>Param2</ns1:StringPart> > </detail> > </SOAP:Fault> > </SOAP:Body> > </SOAP:Envelope> > ================================ > > > 2. echoIntArrayFault > The array echoed back does not use the <value> element as specified in the WSDL, >it uses <item>. The WSDL file on the server appears to be still trying to treat the >arrays as SOAP encoded. > > ==Request====================== > <?xml version="1.0" encoding="UTF-8"?> > <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; >xmlns:xsd="http://www.w3.org/2001/XMLSchema"; >xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> > <soapenv:Body> > <echoIntArrayFaultRequest >xmlns="http://soapinterop.org/types/requestresponse";> > <value xmlns="">1</value> > <value xmlns="">2</value> > <value xmlns="">3</value> > </echoIntArrayFaultRequest> > </soapenv:Body> > </soapenv:Envelope> > ==Response===================== > <?xml version='1.0'?> > <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"; >xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"; >xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; >xmlns:xsd="http://www.w3.org/2001/XMLSchema"; >xmlns:dt="urn:schemas-microsoft-com:datatypes" >xmlns:ds="http://www.w3.org/2000/09/xmldsig#"; >xmlns:xenc="http://www.w3.org/2001/04/xmlenc#"; >xmlns:wsse="http://schemas.xmlsoap.org/ws/2002/07/secext"; >xmlns:ref="http://schemas.xmlsoap.org/ws/2002/04/reference/"; >xmlns:ns2="http://soapinterop.org/types/part"; >xmlns:ns1="http://soapinterop.org/types"; >xmlns:ns0="http://soapinterop.org/types/requestresponse"xmlns:wsdl='services.wsdl' > > <SOAP:Body> > <SOAP:Fault> > <faultcode>SOAP:Server</faultcode> > <faultstring>[Virtuoso SOAP server] echoIntArrayFault</faultstring> > <detail> > <ns2:ArrayOfIntPart> > <ns1:item>1</ns1:item> > <ns1:item>2</ns1:item> > <ns1:item>3</ns1:item> > </ns2:ArrayOfIntPart> > </detail> > </SOAP:Fault> > </SOAP:Body> > </SOAP:Envelope> > =============================== > > > 3. echoMultipleFaults1 AND echoMultipleFaults2 with whichFault = 3 > Same problem as above, <item> used instead of <value> per the WSDL. > > > -- > Tom Jordahl > Macromedia Server Development > > > > -----Original Message----- > From: Mitko Iliev [mailto:imitko@;techno-link.com] > Sent: Thursday, October 31, 2002 8:15 AM > To: [EMAIL PROTECTED] > Subject: [soapbuilders] experimental endpoints from group H, I > > > Hi All, > > I've build the endpoints for round 4 - H and I group, which i wish to announce > for testing. So the WSDL files are : > > *group H - simple - RPC encoding > http://imitko.pv.openlinksw.bg:8890/r4/groupH/simple/rpc/services.wsdl > *group H - simple document/literal encoding > http://imitko.pv.openlinksw.bg:8890/r4/groupH/simple/doc/services.wsdl > * group H - complex , RPC encoding > http://imitko.pv.openlinksw.bg:8890/r4/groupH/complex/rpc/services.wsdl > * group I , XSD tests (SOAP/1.1) > http://imitko.pv.openlinksw.bg:8890/r4/groupI/services.wsdl > > Any feedback will be highly appreciated. > > Thanks a lot, > Mitko > -- Mitko Iliev Email : [EMAIL PROTECTED] Developer Web : http://www.openlinksw.com OpenLink Software Phone : +359 32 637 475 Universal Database Connectivity Technology Providers ----------------------------------------------------------------- This group is a forum for builders of SOAP implementations to discuss implementation and interoperability issues. Please stay on-topic. To unsubscribe from this group, send an email to: [EMAIL PROTECTED] Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
