RE: [SOAP] WSDL getProxy() problem

Looking at http://www.w3.org/TR/wsdl the spec seems pretty clear that the WSDL namespace should have a trailing /, however it also makes clear that the soap:binding should NOT have a trailing /. Looking at the schema definitions it looks like both SCHEMA_SOAP_HTTP (used for soap:binding) and SCHEMA_WSDL_HTTP (used for WSDL namespace) both have a trailing /. So, it seems reasonable to remove the trailing / from the SCHEMA_SOAP_HTTP definition since it follows the spec to the letter and causes everything to start working :) That's my vote and I'm sticking to it. -Javier -----Original Message----- From: Dmitri Vinogradov [mailto:dv@allyoucanthink.de] Sent: Monday, July 14, 2003 12:42 PM To: soap@lists.php.net Subject: Re: [SOAP] WSDL getProxy() problem Hi .* Some words about http namespace in WSDL... in W3C Note (15 March 2001) for WSDL (http://www.w3.org/TR/wsdl) you'll find the following namespace prefixes: http -> http://schemas.xmlsoap.org/wsdl/http/ : WSDL namespace for WSDL HTTP GET & POST binding (1.2 Notational Conventions) ... but in all samples in the same document we see : ... <soap:binding style="document" transport=http://schemas.xmlsoap.org/soap/http /> ... In the section 3.3 soap:binding we read: ... The value of the required transport attribute indicates which transport of SOAP this binding corresponds to. The URI value http://schemas.xmlsoap.org/soap/http corresponds to the HTTP binding in the SOAP specification. Other URIs may be used here to indicate other transports (such as SMTP, FTP, etc.). I have never seen any WSDL documents using http://schemas.xmlsoap.org/wsdl/http/ (with trailing slash) namespace... So i think the possible reason for this confusion either just typo in W3C Recomendation (!?!?) or some of the implementations (.NET?) do not really understand the clause "... The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC-2119 [2]." ;) Me vote for removing this trailing slash from http namespace... Regards DV "Arnaud Limbourg" <arnaud.limbourg@club-internet.fr> schrieb im Newsbeitrag news:20030714182129.73bb706f.arnaud.limbourg@club-internet.fr... > Hi, > > I looked at some ressource on that but could not find any. From what i could see the proper way is with the / at the end. So if it is added to the distribution we may break BC. > > Does anybody have any information on that ? > > Arnaud. > > > Hi again. > > > > Ok, now I've gotten my WSDL webservice to work correctly in PHP, so > > I'm taking the next logical step and testing it with .NET. > > > > Version 0.7.5 fails. After some research I found the following > > page: http://www.gnegg.ch/archives/000050.html which has a > > beautiful explanation > > of why. > > > > I made the same change mentioned in the above page an viola! It > > works with > > ..NET! I also went back and ran my PHP test client to verify that everything > > still worked using PHP, and indeed it does. Don't use java so I > > can't test > > it with Java, but I imagine it would also work. > > > > Does the spec say that the schema should have a trailing /? Should > > the trailing / be removed from all schema's or just > > SCHEMA_SOAP_HTTP? Unfortunately I don't know enough about SOAP yet > > to say, but I thought it > > was worth your attention. Very simple fix for interoperability :) (patch > > is included in the above page, btw). > > > > -Javier > > > > -----Original Message----- > > From: Arnaud Limbourg [mailto:arnaud.limbourg@club-internet.fr] > > Sent: Friday, July 11, 2003 3:31 PM > > To: Shane Caraveo > > Cc: soap@lists.php.net > > Subject: Re: [SOAP] WSDL getProxy() problem > > > > > > Enjoy your vacation then :) > > > > I'll keep you informed ;) > > > > Arnaud. > > > > > > > Unfortunately I'm gone for a week, without email...well, not > > > unfortunate for me ;) When I get settled back in I can dig in if > > > it's not already figured out. > > > Shane > > > > > > Arnaud Limbourg wrote: > > > > > > > Thing is that i don't yet know the source really well, i'm > > > > helping shane who is very busy atm. He should be able to help. > > > > I'll cc him this mail so he may be able to help us. > > > > > > > > Arnaud. > > > > > > > > > > > >>I'm doing my best :) Just getting up to speed with the src now, > > > >>I just downloaded this for the first time yesterday :) > > > >> > > > >>Can you tell me for certain whether or not it would be in the > > > >>client or server? I realize you're busy but that would save me > > > >>an incredibly large amount of time tracking this down. > > > >> > > > >>-Javier > > > >> > > > >>-----Original Message----- > > > >>From: LIMBOURG Arnaud > > > >>[mailto:arnaud.limbourg.prestataire@cegetel.fr] > > > >>Sent: Thursday, July 10, 2003 11:22 PM > > > >>To: soap@lists.php.net > > > >>Subject: RE: [SOAP] WSDL getProxy() problem > > > >> > > > >> > > > >>I'll try to have a look but i can do with some help here. > > > >> > > > >>Arnaud. > > > >> > > > >> > > > >>>Tried it, it appears to work well but I have another bug to > > > >>>report. > > > >>> > > > >>>Notice that the example_server.php doesn't quite work > > > >>>correctly with the wsdl_client.php provided in the > > > >>>distribution, when using echoStruct or echoStructAsSimpleTypes, > > > >>>the scripts return '',0,and 0 for string,int, and float > > > >>>respectively. > > > >>> > > > >>>I haven't managed to trace down where the bug is actually > > > >>>coming from, but the reason it's happening is that the struct > > > >>>as it appears during runtime on the server (in the echoStruct > > > >>>function) is actually a SOAPStruct that > > > >>>contains a property called "inputStruct" which is actually > > > >>>another SOAPStruct (which contains your actual values). > > > >>>Somewhere either on the client or server, the SOAPStruct is > > > >>>being nested into itself in a bizarre > > > >>>manner. This bug only appears to effect complex types, > > > >>>simple types get > > > >>>passed through fine. > > > >> > > > >> > > > >>-- > > > >>PHP Soap Mailing List (http://www.php.net/) > > > >>To unsubscribe, visit: > > > >>http://www.php.net/unsub.php > > > >> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > PHP Soap Mailing List (http://www.php.net/) > > To unsubscribe, visit: http://www.php.net/unsub.php > > > > -- > > PHP Soap Mailing List (http://www.php.net/) > > To unsubscribe, visit: http://www.php.net/unsub.php > > > > -- PHP Soap Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php