phpsoaptoolkit-development Mailing List for PHP Soap (Page 6)
Status: Alpha
Brought to you by:
rodif_bl
You can subscribe to this list here.
2002 |
Jan
|
Feb
|
Mar
|
Apr
(21) |
May
(55) |
Jun
(6) |
Jul
(3) |
Aug
(1) |
Sep
(1) |
Oct
(3) |
Nov
(1) |
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
2004 |
Jan
|
Feb
(1) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
(3) |
Oct
|
Nov
|
Dec
|
2005 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
(2) |
Oct
|
Nov
|
Dec
|
2006 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(4) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
2008 |
Jan
|
Feb
|
Mar
(3) |
Apr
|
May
|
Jun
(2) |
Jul
(2) |
Aug
(1) |
Sep
(7) |
Oct
(7) |
Nov
(26) |
Dec
(32) |
2009 |
Jan
(9) |
Feb
(13) |
Mar
(14) |
Apr
(20) |
May
(39) |
Jun
(21) |
Jul
(26) |
Aug
(9) |
Sep
|
Oct
|
Nov
|
Dec
(8) |
2010 |
Jan
(10) |
Feb
(9) |
Mar
|
Apr
|
May
(3) |
Jun
(3) |
Jul
|
Aug
(2) |
Sep
|
Oct
(1) |
Nov
|
Dec
|
2013 |
Jan
|
Feb
|
Mar
(1) |
Apr
(1) |
May
|
Jun
(1) |
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
From: brad l. <rod...@ya...> - 2002-05-02 17:58:46
|
--- andrey <ahr...@ic...> wrote: > HI, > OK. I'm in. I have also an account on sourceforge - androto but I've no > experience with the system. If that fact can help - ok. > I read your update about the exposed functions and I am very satisfied. I > saw that thing and wanted to ask why it is done in that way. > Something is coming into my mind...Now if I have to add 10 of 15 available > functions I've to write 10 times some kind of register. One idea is to pass > an one dimensional array with names of functions this is alreday done ... this is docuemted too :) $soap->addFunction(array('function_one', 'function_two')); (probably we can have 2 > dimensions where the functions is method of a class) and to register those. this is handled differently.. if you want to expose all methods for a class you have to. $soap->setClass("some_class"); class some_class { function method_one(); function method_two(); } now the soap server will act just like that class will. and you can acually have persitiant objects too... take a look at http://phpsoaptoolkit.sourceforge.net/phpsoap/guide/samples/object/ and http://phpsoaptoolkit.sourceforge.net/phpsoap/guide/samples/session_object/ > So I can declare all exported functions in one array at the beggining of the > file or in some config.php "include". The second idea is to have config XMLs > and to load then as in GLADE library that constructs a GUI at runtime but I > think this will be slow. > You said something about checking first five bytes whether they are <?xml . > I saw another way to check for xml document in the userspace of XMLRPC. > There instead of checking first five bytes, a search for <?xml is done and > the input is read the the position where the string is found but this can be > a performance problem probably. > One remark fot the site : > Here http://phpsoaptoolkit.sourceforge.net/phpsoap/guide/documentation/ the > title is misspelled - "Docuemntation" instead of "Documentation" > Now I'll download the new packages and will give them a try this > evening/night. > Last question. You said the the module cannot be compiled as DSO. What I've > to do to test it under linux - to build php into apache? yeah it can't be compiled as a dso.. it can be compiled in staically.. just your normal configure. ./configure --enable-soap --(other php config options) --with-apache=(apache location) > > Best regards, > Andrey > > ----- Original Message ----- > From: "brad lafountain" <rod...@ya...> > To: <ahr...@ic...> > Sent: Thursday, May 02, 2002 7:48 AM > Subject: php-soap mailing lists > > > > Hello, I noticed that you weren't on the mailing lists. > > > > I would like you to join so you can get my update notices. > > > > > > - Brad > > > > __________________________________________________ > > Do You Yahoo!? > > Yahoo! Health - your guide to health and wellness > > http://health.yahoo.com > > > __________________________________________________ Do You Yahoo!? Yahoo! Health - your guide to health and wellness http://health.yahoo.com |
From: Jean-Charles P. <jc....@wa...> - 2002-05-02 17:43:32
|
Re it's ok there is no crash but when i launch the script below, the httpd daemon is lauched a least 50 times, without any response from the browser i launch hello_world_client.php /* hello_world_client.php */ <?php $hello =3D new SoapObject("http://localhost:8080/hello_world_server.php", "urn:HelloWorld"); echo $hello->hello_soap(); ?> /* hello_world_server.php */ <?php $server =3D new SoapServer("urn:HelloWorld"); $server->addFunction("hello_soap"); $server->handle(); function hello_soap($message){ return "PHP-SOAP=A8says ($message)"; } ?> /* when i run gdb */ web:/opt/serveur/bin# gdb httpd GNU gdb 2002-04-01-cvs Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you = are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for detail= s. This GDB was configured as "i386-linux"...(no debugging symbols found)... (gdb) run -X -f /opt/serveur/conf/httpd.conf Starting program: /opt/serveur/bin/httpd -X -f /opt/serveur/conf/httpd.co= nf (no debugging symbols found)...(no debugging symbols found)...(no debuggi= ng symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debuggi= ng symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debuggi= ng symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debuggi= ng symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debuggi= ng symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debuggi= ng symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debuggi= ng symbols found)...(no debugging symbols found)...(no debugging symbols found)... is it ok ? thx Jean-Charles Preaux =2E ----- Original Message ----- From: "brad lafountain" <rod...@ya...> To: "Jean-Charles Preaux" <jc....@wa...> Cc: <php...@li...> Sent: Thursday, May 02, 2002 5:18 PM Subject: Re: [PHP-SOAP-DEV] 'always_populate_raw_post_data' question > Well... I dunno about that.... > > Can you supply a backtrace... > > gdb httpd > > run -X > > then run the script that cause the crash... > > then type bt... > > this will get you a backtrace and more information for me to go on... > > - Brad > --- Jean-Charles Preaux <jc....@wa...> wrote: > > in fact > > i fust typing the hello_world-server.php in the browser. > > :( > > but when i use hello_world_server.php it crash my web server ...witho= ut any > > response. > > thx > > ----- Original Message ----- > > From: "brad lafountain" <rod...@ya...> > > To: "Jean-Charles Preaux" <jc....@wa...>; > > <php...@li...> > > Sent: Thursday, May 02, 2002 4:36 PM > > Subject: Re: [PHP-SOAP-DEV] 'always_populate_raw_post_data' question > > > > > > > Hmm... are you running a SoapObject against the hello_world-server = or are > > you > > > just typing the hello_world-server.php in the browser directly/comm= and > > line. > > > This is the output you should recieve if you aren't using a SoapObj= ect to > > > access the server. Let me know if this helps > > > > > > - Brad > > > > > > --- Jean-Charles Preaux <jc....@wa...> wrote: > > > > Hello > > > > i try today to use PHP-SOAP extension. > > > > it compiled well (i use php-4.2.0 and apache-1.3.24, libxml2-2.4.= 19, > > > > expat-1.95.2, Sablot-0.90) > > > > i try the "hello world-server.php" script and the output is : > > > > <!-- > > > > <?xml version=3D"1.0" encoding=3D"UTF-8" ?> > > > > - <SOAP-ENV:Envelope > > > > xmlns:SOAP-ENV=3D"http://schemas.xmlsoap.org/soap/envelope/" > > > > SOAP-ENV:encodingStyle=3D"http://schemas.xmlsoap.org/soap/encodin= g/" > > > > xmlns:SOAP-ENC=3D"http://schemas.xmlsoap.org/soap/encoding/" > > > > xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance" > > > > xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema"> > > > > - <SOAP-ENV:Body> > > > > - <SOAP-ENV:Fault xsi:type=3D"SOAP-ENC:Struct"> > > > > <faultstring xsi:type=3D"xsd:string">PHP-SOAP requires > > > > 'always_populate_raw_post_data' to be on please check your php.in= i > > > > file</faultstring> > > > > <faultcode xsi:type=3D"xsd:string">SOAP-ENV:Server</faultcode> > > > > </SOAP-ENV:Fault> > > > > </SOAP-ENV:Body> > > > > </SOAP-ENV:Envelope> > > > > --> > > > > then i create a php.ini with : > > > > always_populate_raw_post_data =3D 1 > > > > but the new output is : > > > > <!-- > > > > <?xml version=3D"1.0" encoding=3D"UTF-8" ?> > > > > - <SOAP-ENV:Envelope > > > > xmlns:SOAP-ENV=3D"http://schemas.xmlsoap.org/soap/envelope/" > > > > SOAP-ENV:encodingStyle=3D"http://schemas.xmlsoap.org/soap/encodin= g/" > > > > xmlns:SOAP-ENC=3D"http://schemas.xmlsoap.org/soap/encoding/" > > > > xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance" > > > > xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema"> > > > > - <SOAP-ENV:Body> > > > > - <SOAP-ENV:Fault xsi:type=3D"SOAP-ENC:Struct"> > > > > <faultstring xsi:type=3D"xsd:string">Couln't find > > > > HTTP_RAW_POST_DATA</faultstring> > > > > <faultcode xsi:type=3D"xsd:string">SOAP-ENV:Server</faultcode> > > > > </SOAP-ENV:Fault> > > > > </SOAP-ENV:Body> > > > > </SOAP-ENV:Envelope> > > > > --> > > > > i don't understand , have i made a mistake ? > > > > thanks > > > > Jean-Charles Preaux > > > > http://analogx.dyndns.org > > > > > > > > > __________________________________________________ > > > Do You Yahoo!? > > > Yahoo! Health - your guide to health and wellness > > > http://health.yahoo.com > > > > > __________________________________________________ > Do You Yahoo!? > Yahoo! Health - your guide to health and wellness > http://health.yahoo.com > > _______________________________________________________________ > > Have big pipes? SourceForge.net is looking for download mirrors. We sup= ply > the hardware. You get the recognition. Email Us: bandwidth@sourceforge.= net > _______________________________________________ > Phpsoaptoolkit-development mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpsoaptoolkit-development |
From: brad l. <rod...@ya...> - 2002-05-02 15:18:02
|
Well... I dunno about that.... Can you supply a backtrace... gdb httpd run -X then run the script that cause the crash... then type bt... this will get you a backtrace and more information for me to go on... - Brad --- Jean-Charles Preaux <jc....@wa...> wrote: > in fact > i fust typing the hello_world-server.php in the browser. > :( > but when i use hello_world_server.php it crash my web server ...without any > response. > thx > ----- Original Message ----- > From: "brad lafountain" <rod...@ya...> > To: "Jean-Charles Preaux" <jc....@wa...>; > <php...@li...> > Sent: Thursday, May 02, 2002 4:36 PM > Subject: Re: [PHP-SOAP-DEV] 'always_populate_raw_post_data' question > > > > Hmm... are you running a SoapObject against the hello_world-server or are > you > > just typing the hello_world-server.php in the browser directly/command > line. > > This is the output you should recieve if you aren't using a SoapObject to > > access the server. Let me know if this helps > > > > - Brad > > > > --- Jean-Charles Preaux <jc....@wa...> wrote: > > > Hello > > > i try today to use PHP-SOAP extension. > > > it compiled well (i use php-4.2.0 and apache-1.3.24, libxml2-2.4.19, > > > expat-1.95.2, Sablot-0.90) > > > i try the "hello world-server.php" script and the output is : > > > <!-- > > > <?xml version="1.0" encoding="UTF-8" ?> > > > - <SOAP-ENV:Envelope > > > xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" > > > SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" > > > 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"> > > > - <SOAP-ENV:Body> > > > - <SOAP-ENV:Fault xsi:type="SOAP-ENC:Struct"> > > > <faultstring xsi:type="xsd:string">PHP-SOAP requires > > > 'always_populate_raw_post_data' to be on please check your php.ini > > > file</faultstring> > > > <faultcode xsi:type="xsd:string">SOAP-ENV:Server</faultcode> > > > </SOAP-ENV:Fault> > > > </SOAP-ENV:Body> > > > </SOAP-ENV:Envelope> > > > --> > > > then i create a php.ini with : > > > always_populate_raw_post_data = 1 > > > but the new output is : > > > <!-- > > > <?xml version="1.0" encoding="UTF-8" ?> > > > - <SOAP-ENV:Envelope > > > xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" > > > SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" > > > 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"> > > > - <SOAP-ENV:Body> > > > - <SOAP-ENV:Fault xsi:type="SOAP-ENC:Struct"> > > > <faultstring xsi:type="xsd:string">Couln't find > > > HTTP_RAW_POST_DATA</faultstring> > > > <faultcode xsi:type="xsd:string">SOAP-ENV:Server</faultcode> > > > </SOAP-ENV:Fault> > > > </SOAP-ENV:Body> > > > </SOAP-ENV:Envelope> > > > --> > > > i don't understand , have i made a mistake ? > > > thanks > > > Jean-Charles Preaux > > > http://analogx.dyndns.org > > > > > > __________________________________________________ > > Do You Yahoo!? > > Yahoo! Health - your guide to health and wellness > > http://health.yahoo.com > __________________________________________________ Do You Yahoo!? Yahoo! Health - your guide to health and wellness http://health.yahoo.com |
From: brad l. <rod...@ya...> - 2002-05-02 14:36:34
|
Hmm... are you running a SoapObject against the hello_world-server or are you just typing the hello_world-server.php in the browser directly/command line. This is the output you should recieve if you aren't using a SoapObject to access the server. Let me know if this helps - Brad --- Jean-Charles Preaux <jc....@wa...> wrote: > Hello > i try today to use PHP-SOAP extension. > it compiled well (i use php-4.2.0 and apache-1.3.24, libxml2-2.4.19, > expat-1.95.2, Sablot-0.90) > i try the "hello world-server.php" script and the output is : > <!-- > <?xml version="1.0" encoding="UTF-8" ?> > - <SOAP-ENV:Envelope > xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" > SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" > 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"> > - <SOAP-ENV:Body> > - <SOAP-ENV:Fault xsi:type="SOAP-ENC:Struct"> > <faultstring xsi:type="xsd:string">PHP-SOAP requires > 'always_populate_raw_post_data' to be on please check your php.ini > file</faultstring> > <faultcode xsi:type="xsd:string">SOAP-ENV:Server</faultcode> > </SOAP-ENV:Fault> > </SOAP-ENV:Body> > </SOAP-ENV:Envelope> > --> > then i create a php.ini with : > always_populate_raw_post_data = 1 > but the new output is : > <!-- > <?xml version="1.0" encoding="UTF-8" ?> > - <SOAP-ENV:Envelope > xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" > SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" > 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"> > - <SOAP-ENV:Body> > - <SOAP-ENV:Fault xsi:type="SOAP-ENC:Struct"> > <faultstring xsi:type="xsd:string">Couln't find > HTTP_RAW_POST_DATA</faultstring> > <faultcode xsi:type="xsd:string">SOAP-ENV:Server</faultcode> > </SOAP-ENV:Fault> > </SOAP-ENV:Body> > </SOAP-ENV:Envelope> > --> > i don't understand , have i made a mistake ? > thanks > Jean-Charles Preaux > http://analogx.dyndns.org __________________________________________________ Do You Yahoo!? Yahoo! Health - your guide to health and wellness http://health.yahoo.com |
From: Jean-Charles P. <jc....@wa...> - 2002-05-02 11:22:29
|
Hello i try today to use PHP-SOAP extension. it compiled well (i use php-4.2.0 and apache-1.3.24, libxml2-2.4.19, = expat-1.95.2, Sablot-0.90) i try the "hello world-server.php" script and the output is :=20 <!-- <?xml version=3D"1.0" encoding=3D"UTF-8" ?>=20 - <SOAP-ENV:Envelope = xmlns:SOAP-ENV=3D"http://schemas.xmlsoap.org/soap/envelope/" = SOAP-ENV:encodingStyle=3D"http://schemas.xmlsoap.org/soap/encoding/" = xmlns:SOAP-ENC=3D"http://schemas.xmlsoap.org/soap/encoding/" = xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance" = xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema"> - <SOAP-ENV:Body> - <SOAP-ENV:Fault xsi:type=3D"SOAP-ENC:Struct"> <faultstring xsi:type=3D"xsd:string">PHP-SOAP requires = 'always_populate_raw_post_data' to be on please check your php.ini = file</faultstring>=20 <faultcode xsi:type=3D"xsd:string">SOAP-ENV:Server</faultcode>=20 </SOAP-ENV:Fault> </SOAP-ENV:Body> </SOAP-ENV:Envelope> --> then i create a php.ini with : always_populate_raw_post_data =3D 1 but the new output is :=20 <!-- <?xml version=3D"1.0" encoding=3D"UTF-8" ?>=20 - <SOAP-ENV:Envelope = xmlns:SOAP-ENV=3D"http://schemas.xmlsoap.org/soap/envelope/" = SOAP-ENV:encodingStyle=3D"http://schemas.xmlsoap.org/soap/encoding/" = xmlns:SOAP-ENC=3D"http://schemas.xmlsoap.org/soap/encoding/" = xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance" = xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema"> - <SOAP-ENV:Body> - <SOAP-ENV:Fault xsi:type=3D"SOAP-ENC:Struct"> <faultstring xsi:type=3D"xsd:string">Couln't find = HTTP_RAW_POST_DATA</faultstring>=20 <faultcode xsi:type=3D"xsd:string">SOAP-ENV:Server</faultcode>=20 </SOAP-ENV:Fault> </SOAP-ENV:Body> </SOAP-ENV:Envelope> --> i don't understand , have i made a mistake ? thanks Jean-Charles Preaux http://analogx.dyndns.org |
From: brad l. <rod...@ya...> - 2002-05-02 05:04:49
|
Ok i have put out a new release. I know that that was quick.. I havn't added that much but i realized i did something that was't good. So i suggest who ever is using it use the new update. What this does... Some handing stuff.. The server useto automatically send a fault when always_populate_raw_post_data was off. Now it will check for HTTP_RAW_POST_DATA first then check the ini setting and if it's off it will finally send the fault saying the ini setting should be on. The client useto deny any request that doesn't have the Content-Type: text/xml. I changed it so that it will check the header first if its not xml it will read the first 5 bytes and see if its xml ("<?xml"). If that is true it will try and process the request normall. By default the server automatically exposed all methods available to php. I changed it so that it doesn't expose any. You now will have to tell the server every function you want exposed. See... http://phpsoaptoolkit.sourceforge.net/phpsoap/guide/documentation/classes/soapserver/addfunction/ You can still expose all methods by calling $soap_server->addFunction(SOAP_FUNCTIONS_ALL); but its not default anymore.. New Features.. On the server side you can now return custom faults.. function do_something($data) { if(!$data) return new SoapFault(string "fault_string" [, string "fault_code"] [, mixed "details] [, "fault_actor]); return "thanks for suppling $data"; } On the client side you can now see the seralized soap call $client->some_soap_call(); echo $client->__getLastMessage(); The big reason for the patch already.. I added php stream handling code for the upcomming streams in php-4.3.0. When i did i change php_close_socket(socket) to close(socket). So all of you client calls are keeping a connection to the server. So if you are calling multiple calls to the same server you will notice a huge performance difference. And i fixed a few mem leaks. And the config.m4 file in the tar ball won't be a tar ball again. A windows binary and tarballs will be posted shortly Enjoy.. keep the feed back comming. -Brad __________________________________________________ Do You Yahoo!? Yahoo! Health - your guide to health and wellness http://health.yahoo.com |
From: brad l. <rod...@ya...> - 2002-05-02 03:21:22
|
--- phpsurf <ph...@if...> wrote: > well, it sounds good ... > new SoapFault ("faultstring", ["faultcode", ]["faultactor", ]["details"]) I am implementing this now... I think i will do.. new SoapFault ("faultstring", ["faultcode", ]["details", ]["faultactor"]) or new SoapFault ("faultstring", ["details", ]["faultcode", ]["faultactor"]) What do you think... The reason for this is i think people will use details more than they will use actor.... > > but maybe, you could take advantage from waiting for the new exception > system in ZendEngine2 ... > > then, we could have several exception classes, extending SoapFault ... > > class MySoapException extends SoapFault { > var $faultcode = "MYAPP:MyCode"; > ... > } > > and then in you soap method: > > throw new MySoapException (); Yeah i want to do alot of stuff with zend two... throwing faults on server and catching faults on client... > > > > -----Original Message----- > From: brad lafountain [mailto:rod...@ya...] > Sent: mardi 30 avril 2002 20:00 > To: phpsurf; php...@li... > Subject: Re: [PHP-SOAP-DEV] Custom Faults > > > > --- phpsurf <ph...@if...> wrote: > > Hi > > > > just a quick question : > > is it possible to throw custom faults on the soap server side ? > > > > the native PHP errors handling is really great ... everything works > without > > having to handle anything ! > > but what if I want to qualify the different types of errors and assign > them > > different FaultCodes ? > > Currently there is no way of doing this. I do have a SoapFault class. I > wanted > to intergrate that on the server side so you could do what you are talking > about. > > How would you suggest the fault code return look. > > function do_something() > { > if(some_status) > return string; > else > return new SoapFault("code", "details"); > } > > > - brad > > > > thx > > > > > > > > ____________________________________________________________________________ > __ > > ifrance.com, l'email gratuit le plus complet de l'Internet ! > > vos emails depuis un navigateur, en POP3, sur Minitel, sur le WAP... > > http://www.ifrance.com/_reloc/email.emailif > > > > > > > > _______________________________________________ > > Phpsoaptoolkit-development mailing list > > Php...@li... > > https://lists.sourceforge.net/lists/listinfo/phpsoaptoolkit-development > > > __________________________________________________ > Do You Yahoo!? > Yahoo! Health - your guide to health and wellness > http://health.yahoo.com > > > ______________________________________________________________________________ > ifrance.com, l'email gratuit le plus complet de l'Internet ! > vos emails depuis un navigateur, en POP3, sur Minitel, sur le WAP... > http://www.ifrance.com/_reloc/email.emailif > > __________________________________________________ Do You Yahoo!? Yahoo! Health - your guide to health and wellness http://health.yahoo.com |
From: brad l. <rod...@ya...> - 2002-05-01 20:44:46
|
I was just doing some more tests. I realized that the client with the current version is way slower than i am use to, I'll let you know what i find. - Brad __________________________________________________ Do You Yahoo!? Yahoo! Health - your guide to health and wellness http://health.yahoo.com |
From: brad l. <rod...@ya...> - 2002-05-01 16:32:17
|
--- andrey <ahr...@ic...> wrote: > Hello Brad, > I am very thankful to you that you created the SOAP extension. I gived it a > try but had only problems. > I didn't succeeded to test even the HelloWord example which I got from the > project's site. > After receiving blank screens in the browser several times, I decided to > debug.Here I spoke for Windows experience -CGI. > I tried to var_dump() the SoapObject and one of the properties was setted - > the fault. The fault was received from the hello_world_server.php so > probably the client part is working well. The message reads that I've to > turn always_populate_raw_post_data on. My example section aren't up to par yet. You can do this on the client side to help determine some faults. $soap->some_call(); if($soap->__isFault()) var_dump($soap->__getFault()); But why it isn't saying that always_populate_raw_post_data is off i don't know. On the server side try var_dump(ini_get("always_popuplate_raw_post_data")); I added that test in there just before i made the release because i know php-4.2.0 uses that and i wanted some kinda test in there. Maybe the test can first test if HTTP_RAW_POST_DATA is available then if not test the ini setting, finally returning a soap fault if it's not set. I moved from 4.1.1 to 4.2.0 with no > success even changing always_populate_raw_post_data to On. I debugged the > server part to be sure that $HTTP_RAW_POST_DATA is populated and > after several atempts do it, I done it. Several attempts because I realized > that no code after $some->handle() in the main program is executed so I > moved mu > debugging code before this call. I wrote the contents of $HTTP_RAW_POST_DATA > in a file using var_export()/ob_*. The var is ok but why the SoarServer > claims that there is an error. > I decided that maybe the problem is under windows and switched to Linux. I > unpacked the zip with the sources and here the problems begun. First the > config.m4 is not .m4 file but a .tar. I needed some time to realize that. Hmm.. ill look into that. > I've problems with compiling because libxml2 path was > /usr/include/libxml2/libxml not /usr/include/libxml. I fixed that with a oh.. my includes are #include <libxml2/*.h> ill can change them. > soft link, and the code started to compile. It compiles well but on > linking(not sure but i think that is the job of libtool) with libtool I got > errors. The errors are about not existents calls to functions. These are > functions from the libxml2 library. it assumes that libxml2 is installed under /usr/local/ http://phpsoaptoolkit.sourceforge.net/phpsoap/guide/documentation/installation/ This is only because i don't know how to use libtool and config.m4 files. I am hoping that someone can enlighten me on configure them. > I'm lost. I was so happy that you released the SOAP extension because I > started working on my bachelor thesis few days ago and I decided previously > that I will use xmlrpc because there is such extension and not to use SOAP > because Dietrich Ayala's SOAP4x, now called NuSOAP is too slow. I'll be glad > if I can help you in any way. Are you familure with the make config process. Currently it doesn't compile as a .so ither because of the config/make process. > May you give me some light what to do. Just to let you know that this extension is very much an alpha release. There are still some leaks/segfaults in there. I am hoping that people like you and others can help me to get this at a stable release as soon as possible. > > Best regards, > Andrey Hristov > __________________________________________________ Do You Yahoo!? Yahoo! Health - your guide to health and wellness http://health.yahoo.com |
From: brad l. <rod...@ya...> - 2002-04-30 22:41:09
|
--- phpsurf <ph...@if...> wrote: > > > -----Original Message----- > > When php-soap starts generating wsdl's it is going to be soley > > dependant on the > > user documenting their code. phpdoc style. Otherwise the wsdl > > generator can't > > know types and parameters. Well I think we are talking about two differnt things here. 1) wsdl generation.. The wsdl has definintions about parameter types and return types. We all know php isn't type specfic. So for php-soap to be able to auto-generate wsdls it needs to know the types of parameters and the return values. So was looking into phpdoc and how to use that. /** Short Desc Long Desc @param name string description @param value string description @returns string description */ function do_something($name, $value) { return $name . $value; } if someone documents their code then php-soap can parse that file and pull the necessary information and genearte a wsdl from that. but that assumes that the developers are going to write their docuemntation correctly. Or i can write a script that will help the user guide thru a process of generating a wsdl. the "wizzard" will prompt them for parameters and return types. 2) php serialization / soap serialziation to and from native php and soap. Currently there is no way to override the way that it will seralize types. I do plan on creating an api to allow the users both on the client and server to override serialization. I havn't thought of a good way of doing it yet. But for the most part im pretty sure you wont need this. The way it currently works right now is. your wsdl defines this <schema> <s:element name="someObject"> <s:complexType> <s:element type="s:string" name="memberOne"> <s:element type="s:string" name="memberTwo"> </s:complexType> </s:element> </schema> and you have this code $server = new SoapServer(); $server->addFunction("returnSomeObject"); $server->bind("/wsdl/location/test.wsdl"); $server->handle(); function returnSomeObject() { $ret->memberOne = 'test'; $ret->memberTwo = 'test'; $ret->memberThree = 'test'; $ret->memberFour = 'test'; return ret; } now anytime someone invokes returnSomeObject it will only serialize memberOne and memberTwo and leave out memberFour and memberFive. and again with types it will auto convert types to the correct values. and with i don't know if you have seen SoapVar. But you can do something like this function getDateTime() { return new SoapVar(time(), XSD_DATETIME); } and that will serialize to the correct date time string that xsd defines. take alook at http://phpsoaptoolkit.sourceforge.net/phpsoap/guide/documentation/classes/soapvar/constructor/ Does this make any sence. If i still need to add a way to override serialziation then i will add it. I just need to come up with a way to give the user a way to define it. - brad > > are you talking about, for example, object creation from soap values, I mean > : how to transform a SoapValue into the apropriate PhpClass/Type ? > > I've been working a litle with the java Apache Soap implementation ... > and they use, on the client side some kind of mapping table which is a > property of each SoapClient. > > and on the server side, they use an xml file called "deployment descriptor" > to describe the java properties of the web services available on the server. > I know this server side on .Net is in the code comments likewhat you suggest > ... > > indeed, it's not really a question :) > I just wanted to know your thinking about that ... > > > ______________________________________________________________________________ > ifrance.com, l'email gratuit le plus complet de l'Internet ! > vos emails depuis un navigateur, en POP3, sur Minitel, sur le WAP... > http://www.ifrance.com/_reloc/email.emailif > > > > _______________________________________________ > Phpsoaptoolkit-development mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpsoaptoolkit-development __________________________________________________ Do You Yahoo!? Yahoo! Health - your guide to health and wellness http://health.yahoo.com |
From: phpsurf <ph...@if...> - 2002-04-30 19:01:04
|
> -----Original Message----- > When php-soap starts generating wsdl's it is going to be soley > dependant on the > user documenting their code. phpdoc style. Otherwise the wsdl > generator can't > know types and parameters. are you talking about, for example, object creation from soap values, I mean : how to transform a SoapValue into the apropriate PhpClass/Type ? I've been working a litle with the java Apache Soap implementation ... and they use, on the client side some kind of mapping table which is a property of each SoapClient. and on the server side, they use an xml file called "deployment descriptor" to describe the java properties of the web services available on the server. I know this server side on .Net is in the code comments likewhat you suggest ... indeed, it's not really a question :) I just wanted to know your thinking about that ... ______________________________________________________________________________ ifrance.com, l'email gratuit le plus complet de l'Internet ! vos emails depuis un navigateur, en POP3, sur Minitel, sur le WAP... http://www.ifrance.com/_reloc/email.emailif |
From: phpsurf <ph...@if...> - 2002-04-30 18:45:46
|
why is it mandatory to have register_globals=On to enable object persistance on the soap server ? couldn't you get rid of that ? because register_globals is now Off by default since 4.2.0 ... and so, many hosters may leave this to Off ! ______________________________________________________________________________ ifrance.com, l'email gratuit le plus complet de l'Internet ! vos emails depuis un navigateur, en POP3, sur Minitel, sur le WAP... http://www.ifrance.com/_reloc/email.emailif |
From: phpsurf <ph...@if...> - 2002-04-30 18:24:54
|
well, it sounds good ... new SoapFault ("faultstring", ["faultcode", ]["faultactor", ]["details"]) but maybe, you could take advantage from waiting for the new exception system in ZendEngine2 ... then, we could have several exception classes, extending SoapFault ... class MySoapException extends SoapFault { var $faultcode = "MYAPP:MyCode"; ... } and then in you soap method: throw new MySoapException (); -----Original Message----- From: brad lafountain [mailto:rod...@ya...] Sent: mardi 30 avril 2002 20:00 To: phpsurf; php...@li... Subject: Re: [PHP-SOAP-DEV] Custom Faults --- phpsurf <ph...@if...> wrote: > Hi > > just a quick question : > is it possible to throw custom faults on the soap server side ? > > the native PHP errors handling is really great ... everything works without > having to handle anything ! > but what if I want to qualify the different types of errors and assign them > different FaultCodes ? Currently there is no way of doing this. I do have a SoapFault class. I wanted to intergrate that on the server side so you could do what you are talking about. How would you suggest the fault code return look. function do_something() { if(some_status) return string; else return new SoapFault("code", "details"); } - brad > > thx > > > ____________________________________________________________________________ __ > ifrance.com, l'email gratuit le plus complet de l'Internet ! > vos emails depuis un navigateur, en POP3, sur Minitel, sur le WAP... > http://www.ifrance.com/_reloc/email.emailif > > > > _______________________________________________ > Phpsoaptoolkit-development mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpsoaptoolkit-development __________________________________________________ Do You Yahoo!? Yahoo! Health - your guide to health and wellness http://health.yahoo.com ______________________________________________________________________________ ifrance.com, l'email gratuit le plus complet de l'Internet ! vos emails depuis un navigateur, en POP3, sur Minitel, sur le WAP... http://www.ifrance.com/_reloc/email.emailif |
From: brad l. <rod...@ya...> - 2002-04-30 18:11:40
|
The WSDLGenerator isn't even close to done yet... I was looking at that last night. I think i want to incorperate that directly into the ext/soap module without having an external php script. I was looking at pear/PECL/phpdoc that is a c-level script parser that will allow me to what i am talking about. This might take a while to incorperate. But here is a suggestion.. If you are familure with Java. goto http://www.themindelectric.com/ and download their glue product. This product comes with a java2wsdl. You can create a dummy class and generate a wsdl against it then just use that for you php-soap server. here is an example. mytest.java public interface mytest { String getValue(); void setValue(String value); } compile that java code and run java2wsdl mytest it will create a wsdl for you. change the endpoint to point to your php-soap server. I know it's a hack but it does work. When php-soap starts generating wsdl's it is going to be soley dependant on the user documenting their code. phpdoc style. Otherwise the wsdl generator can't know types and parameters. I might make WSDLGenerator wizard but then it won't be able to generate the WSDL's on the fly. This is a pretty big part of the project and i do understand that it NEEDs to be incorperated. I just need to come up with a good way to do it. I currently am gettin rid of some memleaks and a segfault i found last nite. The wsdl generation is next on my plate. _brad_ --- phpsurf <ph...@if...> wrote: > I cannot get out of the WSDLGenerator ! > do you have any "tutorial" to start with ? > or just some advice ? > > thx > > ______________________________________________________________________________ > ifrance.com, l'email gratuit le plus complet de l'Internet ! > vos emails depuis un navigateur, en POP3, sur Minitel, sur le WAP... > http://www.ifrance.com/_reloc/email.emailif > > > > _______________________________________________ > Phpsoaptoolkit-development mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpsoaptoolkit-development __________________________________________________ Do You Yahoo!? Yahoo! Health - your guide to health and wellness http://health.yahoo.com |
From: brad l. <rod...@ya...> - 2002-04-30 18:00:20
|
--- phpsurf <ph...@if...> wrote: > Hi > > just a quick question : > is it possible to throw custom faults on the soap server side ? > > the native PHP errors handling is really great ... everything works without > having to handle anything ! > but what if I want to qualify the different types of errors and assign them > different FaultCodes ? Currently there is no way of doing this. I do have a SoapFault class. I wanted to intergrate that on the server side so you could do what you are talking about. How would you suggest the fault code return look. function do_something() { if(some_status) return string; else return new SoapFault("code", "details"); } - brad > > thx > > > ______________________________________________________________________________ > ifrance.com, l'email gratuit le plus complet de l'Internet ! > vos emails depuis un navigateur, en POP3, sur Minitel, sur le WAP... > http://www.ifrance.com/_reloc/email.emailif > > > > _______________________________________________ > Phpsoaptoolkit-development mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpsoaptoolkit-development __________________________________________________ Do You Yahoo!? Yahoo! Health - your guide to health and wellness http://health.yahoo.com |
From: phpsurf <ph...@if...> - 2002-04-30 15:18:39
|
I cannot get out of the WSDLGenerator ! do you have any "tutorial" to start with ? or just some advice ? thx ______________________________________________________________________________ ifrance.com, l'email gratuit le plus complet de l'Internet ! vos emails depuis un navigateur, en POP3, sur Minitel, sur le WAP... http://www.ifrance.com/_reloc/email.emailif |
From: phpsurf <ph...@if...> - 2002-04-30 14:40:03
|
Hi just a quick question : is it possible to throw custom faults on the soap server side ? the native PHP errors handling is really great ... everything works without having to handle anything ! but what if I want to qualify the different types of errors and assign them different FaultCodes ? thx ______________________________________________________________________________ ifrance.com, l'email gratuit le plus complet de l'Internet ! vos emails depuis un navigateur, en POP3, sur Minitel, sur le WAP... http://www.ifrance.com/_reloc/email.emailif |
From: phpsurf <ph...@if...> - 2002-04-29 21:43:55
|
cool :) i'm afraid i'm using windows ... :( -----Original Message----- From: php...@li... [mailto:php...@li...]On Behalf Of brad lafountain Sent: lundi 29 avril 2002 23:12 To: phpsurf; php...@li... Subject: [PHP-SOAP-DEV] Re: bug with WSDL: missing operation namespace in the soap request Sweet.. first bug! :) I thought i got rid of thoes damn temps... I'll commit a fix tonite. Are you using windows or linux? if you are using linux then you can just get the cvs otherwise ill have to give you a bindary to keep on testing with. - Brad --- phpsurf <ph...@if...> wrote: > hi > > I'm testing the client with a wsdl ... > case sensitivity and parameter names seem to work fine with the wsdl :) good > point. > > but I got a bug with the following WSDL : > > -------------------------------------------------------------------------- -- > -- > <?xml version="1.0"?> > > <definitions name="BabelFishService" > xmlns:tns="http://www.xmethods.net/sd/BabelFishService.wsdl" > targetNamespace="http://www.xmethods.net/sd/BabelFishService.wsdl" > xmlns:xsd="http://www.w3.org/1999/XMLSchema" > xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" > xmlns="http://schemas.xmlsoap.org/wsdl/"> > > <message name="BabelFishRequest"> > <part name="translationmode" type="xsd:string"/> > <part name="sourcedata" type="xsd:string"/> > </message> > > <message name="BabelFishResponse"> > <part name="return" type="xsd:string"/> > </message> > > <portType name="BabelFishPortType"> > <operation name="BabelFish"> > <input message="tns:BabelFishRequest" name="BabelFish"/> > <output message="tns:BabelFishResponse" name="BabelFishResponse"/> > </operation> > </portType> > > <binding name="BabelFishBinding" type="tns:BabelFishPortType"> > <soap:binding style="rpc" > transport="http://schemas.xmlsoap.org/soap/http"/> > <operation name="BabelFish"> > <soap:operation soapAction="urn:xmethodsBabelFish#BabelFish"/> > <input> > <soap:body use="encoded" namespace="urn:xmethodsBabelFish" > encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/> > </input> > <output> > <soap:body use="encoded" namespace="urn:xmethodsBabelFish" > encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/> > </output> > </operation> > </binding> > > <service name="BabelFish"> > <documentation>Translates text of up to 5k in length, between a variety of > languages.</documentation> > <port name="BabelFishPort" binding="tns:BabelFishBinding"> > <soap:address > location="http://services.xmethods.net:80/perl/soaplite.cgi"/> > </port> > </service> > > </definitions> > -------------------------------------------------------------------------- -- > -- > > the message received by the server is : > see the ***FIXME*** ! > > -------------------------------------------------------------------------- -- > -- > <?xml version="1.0" encoding="UTF-8"?> > <SOAP-ENV:Envelope > xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" > SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" > 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"> > > <SOAP-ENV:Body> > <BabelFish xmlns="***FIXME***"> > <translationmode xsi:type="xsd:string">en_fr</translationmode> > <sourcedata xsi:type="xsd:string">some pretty text to translate > !</sourcedata> > </BabelFish> > </SOAP-ENV:Body> > > </SOAP-ENV:Envelope> > -------------------------------------------------------------------------- -- > -- > > > > ____________________________________________________________________________ __ > ifrance.com, l'email gratuit le plus complet de l'Internet ! > vos emails depuis un navigateur, en POP3, sur Minitel, sur le WAP... > http://www.ifrance.com/_reloc/email.emailif > > __________________________________________________ Do You Yahoo!? Yahoo! Health - your guide to health and wellness http://health.yahoo.com _______________________________________________ Phpsoaptoolkit-development mailing list Php...@li... https://lists.sourceforge.net/lists/listinfo/phpsoaptoolkit-development ______________________________________________________________________________ ifrance.com, l'email gratuit le plus complet de l'Internet ! vos emails depuis un navigateur, en POP3, sur Minitel, sur le WAP... http://www.ifrance.com/_reloc/email.emailif |
From: brad l. <rod...@ya...> - 2002-04-29 21:12:21
|
Sweet.. first bug! :) I thought i got rid of thoes damn temps... I'll commit a fix tonite. Are you using windows or linux? if you are using linux then you can just get the cvs otherwise ill have to give you a bindary to keep on testing with. - Brad --- phpsurf <ph...@if...> wrote: > hi > > I'm testing the client with a wsdl ... > case sensitivity and parameter names seem to work fine with the wsdl :) good > point. > > but I got a bug with the following WSDL : > > ---------------------------------------------------------------------------- > -- > <?xml version="1.0"?> > > <definitions name="BabelFishService" > xmlns:tns="http://www.xmethods.net/sd/BabelFishService.wsdl" > targetNamespace="http://www.xmethods.net/sd/BabelFishService.wsdl" > xmlns:xsd="http://www.w3.org/1999/XMLSchema" > xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" > xmlns="http://schemas.xmlsoap.org/wsdl/"> > > <message name="BabelFishRequest"> > <part name="translationmode" type="xsd:string"/> > <part name="sourcedata" type="xsd:string"/> > </message> > > <message name="BabelFishResponse"> > <part name="return" type="xsd:string"/> > </message> > > <portType name="BabelFishPortType"> > <operation name="BabelFish"> > <input message="tns:BabelFishRequest" name="BabelFish"/> > <output message="tns:BabelFishResponse" name="BabelFishResponse"/> > </operation> > </portType> > > <binding name="BabelFishBinding" type="tns:BabelFishPortType"> > <soap:binding style="rpc" > transport="http://schemas.xmlsoap.org/soap/http"/> > <operation name="BabelFish"> > <soap:operation soapAction="urn:xmethodsBabelFish#BabelFish"/> > <input> > <soap:body use="encoded" namespace="urn:xmethodsBabelFish" > encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/> > </input> > <output> > <soap:body use="encoded" namespace="urn:xmethodsBabelFish" > encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/> > </output> > </operation> > </binding> > > <service name="BabelFish"> > <documentation>Translates text of up to 5k in length, between a variety of > languages.</documentation> > <port name="BabelFishPort" binding="tns:BabelFishBinding"> > <soap:address > location="http://services.xmethods.net:80/perl/soaplite.cgi"/> > </port> > </service> > > </definitions> > ---------------------------------------------------------------------------- > -- > > the message received by the server is : > see the ***FIXME*** ! > > ---------------------------------------------------------------------------- > -- > <?xml version="1.0" encoding="UTF-8"?> > <SOAP-ENV:Envelope > xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" > SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" > 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"> > > <SOAP-ENV:Body> > <BabelFish xmlns="***FIXME***"> > <translationmode xsi:type="xsd:string">en_fr</translationmode> > <sourcedata xsi:type="xsd:string">some pretty text to translate > !</sourcedata> > </BabelFish> > </SOAP-ENV:Body> > > </SOAP-ENV:Envelope> > ---------------------------------------------------------------------------- > -- > > > > ______________________________________________________________________________ > ifrance.com, l'email gratuit le plus complet de l'Internet ! > vos emails depuis un navigateur, en POP3, sur Minitel, sur le WAP... > http://www.ifrance.com/_reloc/email.emailif > > __________________________________________________ Do You Yahoo!? Yahoo! Health - your guide to health and wellness http://health.yahoo.com |
From: phpsurf <ph...@if...> - 2002-04-29 20:57:23
|
hi I'm testing the client with a wsdl ... case sensitivity and parameter names seem to work fine with the wsdl :) good point. but I got a bug with the following WSDL : ---------------------------------------------------------------------------- -- <?xml version="1.0"?> <definitions name="BabelFishService" xmlns:tns="http://www.xmethods.net/sd/BabelFishService.wsdl" targetNamespace="http://www.xmethods.net/sd/BabelFishService.wsdl" xmlns:xsd="http://www.w3.org/1999/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns="http://schemas.xmlsoap.org/wsdl/"> <message name="BabelFishRequest"> <part name="translationmode" type="xsd:string"/> <part name="sourcedata" type="xsd:string"/> </message> <message name="BabelFishResponse"> <part name="return" type="xsd:string"/> </message> <portType name="BabelFishPortType"> <operation name="BabelFish"> <input message="tns:BabelFishRequest" name="BabelFish"/> <output message="tns:BabelFishResponse" name="BabelFishResponse"/> </operation> </portType> <binding name="BabelFishBinding" type="tns:BabelFishPortType"> <soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/> <operation name="BabelFish"> <soap:operation soapAction="urn:xmethodsBabelFish#BabelFish"/> <input> <soap:body use="encoded" namespace="urn:xmethodsBabelFish" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/> </input> <output> <soap:body use="encoded" namespace="urn:xmethodsBabelFish" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/> </output> </operation> </binding> <service name="BabelFish"> <documentation>Translates text of up to 5k in length, between a variety of languages.</documentation> <port name="BabelFishPort" binding="tns:BabelFishBinding"> <soap:address location="http://services.xmethods.net:80/perl/soaplite.cgi"/> </port> </service> </definitions> ---------------------------------------------------------------------------- -- the message received by the server is : see the ***FIXME*** ! ---------------------------------------------------------------------------- -- <?xml version="1.0" encoding="UTF-8"?> <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" 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"> <SOAP-ENV:Body> <BabelFish xmlns="***FIXME***"> <translationmode xsi:type="xsd:string">en_fr</translationmode> <sourcedata xsi:type="xsd:string">some pretty text to translate !</sourcedata> </BabelFish> </SOAP-ENV:Body> </SOAP-ENV:Envelope> ---------------------------------------------------------------------------- -- ______________________________________________________________________________ ifrance.com, l'email gratuit le plus complet de l'Internet ! vos emails depuis un navigateur, en POP3, sur Minitel, sur le WAP... http://www.ifrance.com/_reloc/email.emailif |
From: Jani T. <sn...@ik...> - 2002-04-29 19:49:11
|
Can you stop posting this stuff to ph...@li... please? --Jani On Mon, 29 Apr 2002, phpsurf wrote: >great ... >it looks like using the wsdl will solve some problems ! >but sometimes, specially during development, it is quite fastidious to have >to write a wsdl to make the soap implementation work properly ... because >SOAP has not been defined in the shadow of WSDL ... they are two independant >standards ! >anyway, i will have a look on the wsdl feature ... is it yet ready to use ? > >for my first point, I was not talking about the soap proxy, but about the >HTTP Proxy that some servers may use to connect to the internet ... this is >quite often the situation when working on a corporate server ... >for example, in my company, we can only direct connect to intranet HTTP >servers, when you need to go surfing on some web site outside the intranet, >you need to get it through the HTTP proxy ... >I was talking about the proxy to use when making the HTTP POST request to >the soap server. >do you better see what I mean ? > > >-----Original Message----- >From: brad lafountain [mailto:rod...@ya...] >Sent: lundi 29 avril 2002 19:58 >To: phpsurf; php...@li... >Cc: brad lafountain; ph...@li... >Subject: Re: [PHP-SOAP-DEV] [PHP-DEV] [NEW-EXTENSION]ext/soap : first >play around ... > > > >--- phpsurf <ph...@if...> wrote: >> Hi ! >> >> I just started to play with your new extension as soon as I saw your mail >> this morning on PHP-DEV ! >> >> It's really a good job and I am very impatient to play with the final >> release ... >> >> here are a few suggestions/bugs/requests to help you make this ext really >> great : >> >> - nice to have : a proxy set up for soap requests >> something like : >> >> $client = new SoapObject("uri", "urn"); >> $client->setProxy("proxyUri", 8080); > >what is the uri for in the soap constructor for?... >currently the first parameter is the uri of the proxy. > >$client = new SoapObject("http://proxy.endpoint.com:8080/test.php", >"urn:test"); >that is the use without wsdls... >or >$client = new SoapObject("http://proxy.endpoint.com:8080/test.wsdl"); >then the wsdl will have to define the endpoint > > > >> ... >> >> - bug : but this bug way come from PHP and not from the ext ... >> this deals with case-sensitivity of function names ! >> this reminds me a quite long thread on PHP-DEV about that a few weeks ago >! >> :) >> >> $myObject = new >> >SoapObject("http://www.localhost.com/PhpSoapToolkit/samples/object-server-sr >> c.php", "urn:Object"); >> echo $myObject->getData(); >> >> the method name getData is used to write the XML request ... >> but as function names are not case sensitive, this gives the following XML >> tag : >> <getdata xmlns="urn:Object" ... >> >> and then this doesn't work when you try to call a SOAP server that is not >> writen in PHP ! >> because in SOAP, method names are case-sensitive ! > > Yeah i understand the problems with this.... I'm not sure how this would >work >seeing that when you use a WSDL this is taken care of. > >$soapobject = new SoapObject("http://www.server.com/server.wsdl"); >$soapobject->getData(); > >if the wsdl defines the getData method in uppercase then it will send ><getData .... instead of <getdata .... > >Most soap implementations use wsdl's now-a-days. > >But i will keep that in mind. > >> >> - important feature : the ability to pass named parameters ... >> insteed of having parameters called param0, param1, param2, ... it would >be >> very usefull to have the ability to specify the name of the parameter. >> once again, this would allow to be SOAP-compliant with other systems not >> running PHP. > > Again when using wsdl's it will use the name of the parameter that the wsdl >supplies it. If this is a huge consern that the server you are talking to >doesn't use wsdls and needs named parameters. give me the implementation and >specfics and ill look into it further. > > >I tried to make the client code clean as possible with out stuff like >$soap->call_method("getData"); >and >$soap->set_param_name("data"); > >it is soo much cleaner to read >$soap->getData(); > >and the functionality is there when using wsdls. > >> >> that's all for the moment :) >> >> once again, good job ! >> > > thanks for the feedback.... > >Let me know if you still have a consern about the above issues if the wsdl >support does do what you will need. > > > _brad_ > > >__________________________________________________ >Do You Yahoo!? >Yahoo! Health - your guide to health and wellness >http://health.yahoo.com > > >______________________________________________________________________________ >ifrance.com, l'email gratuit le plus complet de l'Internet ! >vos emails depuis un navigateur, en POP3, sur Minitel, sur le WAP... >http://www.ifrance.com/_reloc/email.emailif > > > > -- |
From: phpsurf <ph...@if...> - 2002-04-29 19:43:07
|
ok, good to know about authentication and proxy ... I'll have a look on the wsdl too and keep you informed ... tanks -----Original Message----- From: brad lafountain [mailto:rod...@ya...] Sent: lundi 29 avril 2002 21:24 To: phpsurf; php...@li... Subject: RE: [PHP-SOAP-DEV] [PHP-DEV] [NEW-EXTENSION]ext/soap : first play around ... --- phpsurf <ph...@if...> wrote: > great ... > it looks like using the wsdl will solve some problems ! > but sometimes, specially during development, it is quite fastidious to have > to write a wsdl to make the soap implementation work properly ... because > SOAP has not been defined in the shadow of WSDL ... they are two independant > standards ! > anyway, i will have a look on the wsdl feature ... is it yet ready to use ? The wsdl "works" i guess. :) That is one of the reasons i wanted to get a release. I found myself just testing wsdls and seeing if they work. So i guess some do some wont but that is what the release is for to get out some of the problems. So try some wsdls and see if they work if they don't email me the wsdl and ill poke around. You can also bind the wsdl to a SoapServer too.. the server will read the definitions of the wsdl and try to output the data occording to the wsdl. This is usefull for interop from a non-php-client to a php-server. I do understand your consern about the testing development of servers/clients using wsdls but i am hoping that the auto generation of wsdls will ease on this type of useage. fear not if this consern is brought up by more developers then i will lookin to a good api for this type of feature. > > for my first point, I was not talking about the soap proxy, but about the > HTTP Proxy that some servers may use to connect to the internet ... this is > quite often the situation when working on a corporate server ... > for example, in my company, we can only direct connect to intranet HTTP > servers, when you need to go surfing on some web site outside the intranet, > you need to get it through the HTTP proxy ... > I was talking about the proxy to use when making the HTTP POST request to > the soap server. > do you better see what I mean ? Oh yes.... Sorry... I do plan on supporting Http proxy with authication too. Its just not implemented yet. _brad_ __________________________________________________ Do You Yahoo!? Yahoo! Health - your guide to health and wellness http://health.yahoo.com ______________________________________________________________________________ ifrance.com, l'email gratuit le plus complet de l'Internet ! vos emails depuis un navigateur, en POP3, sur Minitel, sur le WAP... http://www.ifrance.com/_reloc/email.emailif |
From: brad l. <rod...@ya...> - 2002-04-29 19:24:29
|
--- phpsurf <ph...@if...> wrote: > great ... > it looks like using the wsdl will solve some problems ! > but sometimes, specially during development, it is quite fastidious to have > to write a wsdl to make the soap implementation work properly ... because > SOAP has not been defined in the shadow of WSDL ... they are two independant > standards ! > anyway, i will have a look on the wsdl feature ... is it yet ready to use ? The wsdl "works" i guess. :) That is one of the reasons i wanted to get a release. I found myself just testing wsdls and seeing if they work. So i guess some do some wont but that is what the release is for to get out some of the problems. So try some wsdls and see if they work if they don't email me the wsdl and ill poke around. You can also bind the wsdl to a SoapServer too.. the server will read the definitions of the wsdl and try to output the data occording to the wsdl. This is usefull for interop from a non-php-client to a php-server. I do understand your consern about the testing development of servers/clients using wsdls but i am hoping that the auto generation of wsdls will ease on this type of useage. fear not if this consern is brought up by more developers then i will lookin to a good api for this type of feature. > > for my first point, I was not talking about the soap proxy, but about the > HTTP Proxy that some servers may use to connect to the internet ... this is > quite often the situation when working on a corporate server ... > for example, in my company, we can only direct connect to intranet HTTP > servers, when you need to go surfing on some web site outside the intranet, > you need to get it through the HTTP proxy ... > I was talking about the proxy to use when making the HTTP POST request to > the soap server. > do you better see what I mean ? Oh yes.... Sorry... I do plan on supporting Http proxy with authication too. Its just not implemented yet. _brad_ __________________________________________________ Do You Yahoo!? Yahoo! Health - your guide to health and wellness http://health.yahoo.com |
From: phpsurf <ph...@if...> - 2002-04-29 19:12:04
|
great ... it looks like using the wsdl will solve some problems ! but sometimes, specially during development, it is quite fastidious to have to write a wsdl to make the soap implementation work properly ... because SOAP has not been defined in the shadow of WSDL ... they are two independant standards ! anyway, i will have a look on the wsdl feature ... is it yet ready to use ? for my first point, I was not talking about the soap proxy, but about the HTTP Proxy that some servers may use to connect to the internet ... this is quite often the situation when working on a corporate server ... for example, in my company, we can only direct connect to intranet HTTP servers, when you need to go surfing on some web site outside the intranet, you need to get it through the HTTP proxy ... I was talking about the proxy to use when making the HTTP POST request to the soap server. do you better see what I mean ? -----Original Message----- From: brad lafountain [mailto:rod...@ya...] Sent: lundi 29 avril 2002 19:58 To: phpsurf; php...@li... Cc: brad lafountain; ph...@li... Subject: Re: [PHP-SOAP-DEV] [PHP-DEV] [NEW-EXTENSION]ext/soap : first play around ... --- phpsurf <ph...@if...> wrote: > Hi ! > > I just started to play with your new extension as soon as I saw your mail > this morning on PHP-DEV ! > > It's really a good job and I am very impatient to play with the final > release ... > > here are a few suggestions/bugs/requests to help you make this ext really > great : > > - nice to have : a proxy set up for soap requests > something like : > > $client = new SoapObject("uri", "urn"); > $client->setProxy("proxyUri", 8080); what is the uri for in the soap constructor for?... currently the first parameter is the uri of the proxy. $client = new SoapObject("http://proxy.endpoint.com:8080/test.php", "urn:test"); that is the use without wsdls... or $client = new SoapObject("http://proxy.endpoint.com:8080/test.wsdl"); then the wsdl will have to define the endpoint > ... > > - bug : but this bug way come from PHP and not from the ext ... > this deals with case-sensitivity of function names ! > this reminds me a quite long thread on PHP-DEV about that a few weeks ago ! > :) > > $myObject = new > SoapObject("http://www.localhost.com/PhpSoapToolkit/samples/object-server-sr > c.php", "urn:Object"); > echo $myObject->getData(); > > the method name getData is used to write the XML request ... > but as function names are not case sensitive, this gives the following XML > tag : > <getdata xmlns="urn:Object" ... > > and then this doesn't work when you try to call a SOAP server that is not > writen in PHP ! > because in SOAP, method names are case-sensitive ! Yeah i understand the problems with this.... I'm not sure how this would work seeing that when you use a WSDL this is taken care of. $soapobject = new SoapObject("http://www.server.com/server.wsdl"); $soapobject->getData(); if the wsdl defines the getData method in uppercase then it will send <getData .... instead of <getdata .... Most soap implementations use wsdl's now-a-days. But i will keep that in mind. > > - important feature : the ability to pass named parameters ... > insteed of having parameters called param0, param1, param2, ... it would be > very usefull to have the ability to specify the name of the parameter. > once again, this would allow to be SOAP-compliant with other systems not > running PHP. Again when using wsdl's it will use the name of the parameter that the wsdl supplies it. If this is a huge consern that the server you are talking to doesn't use wsdls and needs named parameters. give me the implementation and specfics and ill look into it further. I tried to make the client code clean as possible with out stuff like $soap->call_method("getData"); and $soap->set_param_name("data"); it is soo much cleaner to read $soap->getData(); and the functionality is there when using wsdls. > > that's all for the moment :) > > once again, good job ! > thanks for the feedback.... Let me know if you still have a consern about the above issues if the wsdl support does do what you will need. _brad_ __________________________________________________ Do You Yahoo!? Yahoo! Health - your guide to health and wellness http://health.yahoo.com ______________________________________________________________________________ ifrance.com, l'email gratuit le plus complet de l'Internet ! vos emails depuis un navigateur, en POP3, sur Minitel, sur le WAP... http://www.ifrance.com/_reloc/email.emailif |
From: brad l. <rod...@ya...> - 2002-04-29 18:26:34
|
--- Harald Radi <har...@nm...> wrote: > hi brad, > > looks promising. if you intend to port it to php5 (one day ;) pease take > a look at ext/rpc first which is intended to be a framework for exactly > such extensions as the soap toolkit. I just looked at the ext/rpc. Thats pretty cool I was wondering how long it would take me to port that to ZendEngine2. That should help me out tremendisouly. Brad __________________________________________________ Do You Yahoo!? Yahoo! Health - your guide to health and wellness http://health.yahoo.com |