Thread: [PHP-SOAP-DEV] [PHP-DEV] [NEW-EXTENSION]ext/soap : first play around ...
Status: Alpha
Brought to you by:
rodif_bl
Menu
▾
▴
phpsoaptoolkit-development
|
From: phpsurf <ph...@if...> - 2002-04-29 17:12:56
|
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);
...
- 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 !
- 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.
that's all for the moment :)
once again, good job !
______________________________________________________________________________
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 17:58:12
|
--- 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
|
|
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 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: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: 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 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: 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 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: 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-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: 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: 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 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: 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-05-05 00:29:41
|
right, we are talking about several things here ! :) 1- wsdl auto-generation: ok, good idea, I have no other experience of this (only played with java implementation which is type specific ...) 2- php/soap serialization/deserialization: indeed wsdl defines the soap type of a soap parameter, but my point here is: how to determine the corresponding php type ? As they do in the Apache java implementation of soap, we could have a mapping table that would associate each soap type with a php type ... and we could also be able to define our own serializer/deserializer function ... something that would tell php_soap (for a specific instance of soap server): "every time you receive a soap type 'mySchemaSoapType' (as defined is the schema part of the wsdl), deserialize it into the following php type 'myPhpClass' (which would be an existing class, or any php type code), using the deserializer handler 'mySoapToPhpDeserializerFunction' (wich is an existing function)" this definition could run-time on client side and setup (a specific xml document/ or comments in the code) on server side or simply run-time on both client and server side ... for example, one can define a bean_serializer which will only send via soap attributes of an object that have a getter method ... maybe you could have a look at the Apache Implementation of Soap in Java to see how they handled this problematic ... I think their aproach is very attractive because it really let the developer do what he wants with the soap implementation ... this is very powerfull ! http://xml.apache.org/soap/index.html > -----Original Message----- > From: brad lafountain [mailto:rod...@ya...] > Sent: mercredi 1 mai 2002 00:41 > To: phpsurf; php...@li... > Subject: RE: [PHP-SOAP-DEV] WSDLGenerator > > > > --- 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 ______________________________________________________________________________ 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-05-05 05:23:58
|
--- phpsurf <ph...@if...> wrote:
> right, we are talking about several things here ! :)
>
> 1- wsdl auto-generation:
> ok, good idea, I have no other experience of this (only played with java
> implementation which is type specific ...)
Yeah this topic is going to be hard. Im going to try and implements something
here. Its not going to be as good as the java stuff becuase of the type stuff.
but maybe it can adventuall be useful.
Im not sure if you know this but you can currently bind your service to a
existing wsdl.
<?
$server = new SoapServer(...);
$server->bind("some_wsdl.wsdl");
$server->handle();
?>
This does a little magic. If your wsdl defines types in the schema part.
php-saop will try and "convert" the type automatically according to the type in
the wsdl.
Say the wsdl defines
<message name="getShort">
<part name="Result" type="xsd:short" />
</message>
and the php function
function getShort()
{
return "123";
}
php-soap would return the message with the xsd:short type not the xsd:string.
again this is only done when binding to a wsdl.
This also works with complex types.
<complexType name="someType">
<all>
<element name="short" type="xsd:short" />
<element name="string" type="xsd:string" />
</all>
</complexType>
<message name="getType">
<part name="Result" type="someType" />
</message>
function getType()
{
$ret->string = "some string";
$ret->short = "123";
$ret->double 1.3;
return $ret;
}
php-soap will return the type as someType and add string as xsd:string and
short as xsd:short but leave out the double.
I think this is pretty flexable and powerfull, but this functionality is still
pretty experimental. I need to get how that works documented. That also works
on the client side.
$soap = new SoapObject("somewsdl.wsdl");
$soap->echoShort("1234");
What i did just add today is the abilty to do this.
http://server.com/some_php_service.php?WSDL (.net style)
and if there is a wsdl bound to that service it will output the wsdl.
>
> 2- php/soap serialization/deserialization:
> indeed wsdl defines the soap type of a soap parameter, but my point here is:
> how to determine the corresponding php type ?
> As they do in the Apache java implementation of soap, we could have a
> mapping table that would associate each soap type with a php type ... and we
> could also be able to define our own serializer/deserializer function ...
> something that would tell php_soap (for a specific instance of soap server):
> "every time you receive a soap type 'mySchemaSoapType' (as defined is the
> schema part of the wsdl), deserialize it into the following php type
> 'myPhpClass' (which would be an existing class, or any php type code),
> using the deserializer handler 'mySoapToPhpDeserializerFunction' (wich is an
> existing function)"
>
> this definition could run-time on client side and setup (a specific xml
> document/ or comments in the code) on server side
> or simply run-time on both client and server side ...
> for example, one can define a bean_serializer which will only send via soap
> attributes of an object that have a getter method ...
>
> maybe you could have a look at the Apache Implementation of Soap in Java to
> see how they handled this problematic ...
> I think their aproach is very attractive because it really let the developer
> do what he wants with the soap implementation ... this is very powerfull !
> http://xml.apache.org/soap/index.html
If the above small sample made any sence. the php-to-xml can be handled by
using wsdls but the xml-to-php only seralizes to stdobjects and standard php
types. A api would be pretty nice for this functionality. I do use apache soap
i haven't go into the custom seriazlation.
- Brad
>
>
> > -----Original Message-----
> > From: brad lafountain [mailto:rod...@ya...]
> > Sent: mercredi 1 mai 2002 00:41
> > To: phpsurf; php...@li...
> > Subject: RE: [PHP-SOAP-DEV] WSDLGenerator
> >
> >
> >
> > --- 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
>
>
>
______________________________________________________________________________
> 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
>
>
>
> _______________________________________________________________
>
> Have big pipes? SourceForge.net is looking for download mirrors. We supply
> the hardware. You get the recognition. Email Us: ban...@so...
> _______________________________________________
>
=== message truncated ===
__________________________________________________
Do You Yahoo!?
Yahoo! Health - your guide to health and wellness
http://health.yahoo.com
|
|
From: phpsurf <ph...@if...> - 2002-05-05 11:10:46
|
> -----Original Message-----
> From: brad lafountain [mailto:rod...@ya...]
> Sent: dimanche 5 mai 2002 07:24
> To: phpsurf
> Cc: php...@li...
> Subject: RE: [PHP-SOAP-DEV] WSDLGenerator
>
>
>
> --- phpsurf <ph...@if...> wrote:
> > right, we are talking about several things here ! :)
> >
> > 1- wsdl auto-generation:
> > ok, good idea, I have no other experience of this (only played with java
> > implementation which is type specific ...)
>
> Yeah this topic is going to be hard. Im going to try and
> implements something
> here. Its not going to be as good as the java stuff becuase of
> the type stuff.
> but maybe it can adventuall be useful.
>
> Im not sure if you know this but you can currently bind your service to a
> existing wsdl.
> <?
> $server = new SoapServer(...);
> $server->bind("some_wsdl.wsdl");
> $server->handle();
> ?>
>
> This does a little magic. If your wsdl defines types in the schema part.
> php-saop will try and "convert" the type automatically according
> to the type in
> the wsdl.
>
> Say the wsdl defines
> <message name="getShort">
> <part name="Result" type="xsd:short" />
> </message>
>
> and the php function
>
> function getShort()
> {
> return "123";
> }
>
> php-soap would return the message with the xsd:short type not the
> xsd:string.
> again this is only done when binding to a wsdl.
>
> This also works with complex types.
> <complexType name="someType">
> <all>
> <element name="short" type="xsd:short" />
> <element name="string" type="xsd:string" />
> </all>
> </complexType>
>
> <message name="getType">
> <part name="Result" type="someType" />
> </message>
>
> function getType()
> {
> $ret->string = "some string";
> $ret->short = "123";
> $ret->double 1.3;
> return $ret;
> }
>
> php-soap will return the type as someType and add string as xsd:string and
> short as xsd:short but leave out the double.
>
> I think this is pretty flexable and powerfull, but this
> functionality is still
> pretty experimental. I need to get how that works documented.
> That also works
> on the client side.
>
> $soap = new SoapObject("somewsdl.wsdl");
> $soap->echoShort("1234");
Right, this is already a pretty good job !
What I meant is just the ability to override this default serialization
process with some custom handler.
This is specially usefull in complex services when you want to work with
some kind of beans ... because you can add some controls, or actions like
countings or locking, or adding framework-level parameters like for security
or debug ... when passing your objects to the soap service.
I've been working on a quite big project using apache soap and this kind of
stuff has been very very useful because it let us implement a complex
framework above the apache soap to do all the technical stuff, and then
developers only had to deal with the business aspect of the service ...
>
>
> What i did just add today is the abilty to do this.
> http://server.com/some_php_service.php?WSDL (.net style)
> and if there is a wsdl bound to that service it will output the wsdl.
>
don't seen it yet ...
gonna have a look
> >
> > 2- php/soap serialization/deserialization:
> > indeed wsdl defines the soap type of a soap parameter, but my
> point here is:
> > how to determine the corresponding php type ?
> > As they do in the Apache java implementation of soap, we could have a
> > mapping table that would associate each soap type with a php
> type ... and we
> > could also be able to define our own serializer/deserializer
> function ...
> > something that would tell php_soap (for a specific instance of
> soap server):
> > "every time you receive a soap type 'mySchemaSoapType' (as
> defined is the
> > schema part of the wsdl), deserialize it into the following php type
> > 'myPhpClass' (which would be an existing class, or any php type code),
> > using the deserializer handler
> 'mySoapToPhpDeserializerFunction' (wich is an
> > existing function)"
> >
> > this definition could run-time on client side and setup (a specific xml
> > document/ or comments in the code) on server side
> > or simply run-time on both client and server side ...
> > for example, one can define a bean_serializer which will only
> send via soap
> > attributes of an object that have a getter method ...
> >
> > maybe you could have a look at the Apache Implementation of
> Soap in Java to
> > see how they handled this problematic ...
> > I think their aproach is very attractive because it really let
> the developer
> > do what he wants with the soap implementation ... this is very
> powerfull !
> > http://xml.apache.org/soap/index.html
>
> If the above small sample made any sence. the php-to-xml can be
> handled by
> using wsdls but the xml-to-php only seralizes to stdobjects and
> standard php
> types.
this is where I suggested a mapping table (eg: the soap mapping registry in
apache soap)
to define the right php class for a specific xsd type.
> A api would be pretty nice for this functionality. I do
> use apache soap
> i haven't go into the custom seriazlation.
>
I did mostly use bean serialization and complex types with several actions
in the getter/setter methods.
this could be really good stuff to have this :)
maybe you can even find something better than apache did ...
> - Brad
>
______________________________________________________________________________
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: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 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-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: phpsurf <ph...@if...> - 2002-05-04 23:51:41
|
Hi !
I'm just coming back from some days off to the beach ...
great to hear you're planning to play with ZE2 :)
I have no preference for SoapFault params order ... 'till we can still call
it
new SoapFault ("faultstring", null, "faultcode", null) or anything like that
...
> -----Original Message-----
> From: php...@li...
> [mailto:php...@li...]On Behalf
> Of brad lafountain
> Sent: jeudi 2 mai 2002 05:21
> To: phpsurf; php...@li...
> Subject: RE: [PHP-SOAP-DEV] Custom Faults
>
>
>
> --- 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
_______________________________________________________________
Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: ban...@so...
_______________________________________________
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: phpsurf <ph...@if...> - 2002-05-05 01:05:26
|
well ...
I've just restored my test scripts and added some new custom errors after
installing the last release 0.1.1, and
they don't work !
return new SoapFault("my error message !");
makes PHP crash ! :(
(working on Windows 2000 + Apache 1.23 + PHP 4.2.0 + Php_Soap 0.1.1)
> -----Original Message-----
> From: php...@li...
> [mailto:php...@li...]On Behalf
> Of brad lafountain
> Sent: jeudi 2 mai 2002 05:21
> To: phpsurf; php...@li...
> Subject: RE: [PHP-SOAP-DEV] Custom Faults
>
>
>
> --- 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
_______________________________________________________________
Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: ban...@so...
_______________________________________________
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: phpsurf <ph...@if...> - 2002-05-05 01:17:11
|
to help you on that bug :
return new SoapFault("my error message !");
makes PHP crash;
but
return new SoapFault("my error message !", null, null, null);
seems to work fine ...
some problem with the default values, i guess ...
> -----Original Message-----
> From: php...@li...
> [mailto:php...@li...]On Behalf
> Of phpsurf
> Sent: dimanche 5 mai 2002 03:16
> To: brad lafountain; php...@li...
> Subject: RE: [PHP-SOAP-DEV] Custom Faults
>
>
> well ...
> I've just restored my test scripts and added some new custom errors after
> installing the last release 0.1.1, and
> they don't work !
> return new SoapFault("my error message !");
> makes PHP crash ! :(
>
> (working on Windows 2000 + Apache 1.23 + PHP 4.2.0 + Php_Soap 0.1.1)
>
> > -----Original Message-----
> > From: php...@li...
> > [mailto:php...@li...]On Behalf
> > Of brad lafountain
> > Sent: jeudi 2 mai 2002 05:21
> > To: phpsurf; php...@li...
> > Subject: RE: [PHP-SOAP-DEV] Custom Faults
> >
> >
> >
> > --- 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
>
> _______________________________________________________________
>
> Have big pipes? SourceForge.net is looking for download mirrors. We supply
> the hardware. You get the recognition. Email Us: ban...@so...
> _______________________________________________
> 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
>
>
>
> _______________________________________________________________
>
> Have big pipes? SourceForge.net is looking for download mirrors. We supply
> the hardware. You get the recognition. Email Us: ban...@so...
> _______________________________________________
> 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: phpsurf <ph...@if...> - 2002-05-09 22:02:15
|
hi I've been testing this again with the babelfish and google services ... and I'm afraid the bug is still here ! Don't know if the fix had been included in your second release or not yet ... > -----Original Message----- > From: brad lafountain [mailto:rod...@ya...] > Sent: lundi 29 avril 2002 23:12 > To: phpsurf; php...@li... > Subject: 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 ______________________________________________________________________________ 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 |
Thanks for helping keep SourceForge clean.
X