Re: [SOAP] .NET application communicate with PHP by using SOAP?

Adding some little-Euro-coins too ;-) > > * WSDL support (generated) is currently not in the PEAR::SOAP > implementation > > - When or will this be available > > When PHP starts being a strongly typed language like java <grin>. Now > seriously, one idea that Shane had was to parse the javadoc-style comments that > tools like phpDocumentor parse to generate documentation, now even in peardoc2 > format (a variation of DocBook). The latter could be converted into a WSDL w/ > some XSLT magic, in principle (volunteers? ;-). WSDL seems handy when you want to offer a contract to a consuming party. It is possible with the current implentationt to define the input and output parameters. I think it is easier (my opinion) to generate from this information the WSDL . Actually PEAR::SOAP was based on NuSOAP. NuSOAP actually does support some kind of WSDL generation, although I don't know how it behaves with Complex-types. Side question: What is the current relation (and future relation) of the PEAR::SOAP, NuSoap and the native implementation from Brad ? > If you really need WSDL right now there are different tools available, and the > trick is to create an abstract java class that has the same methods as your PHP > one. There are several emails in the archives on this respect and one I can > remember from PEAR-GENERAL that I wrote: > > > http://news.php.net/article.php?group=php.pear.general&article=3010 I've read this article and I'am familiar with Apache-Axis. Although Sometimes PHP is very handy for short-handed implementations. > > * Doc/Lit support is not available. This makes PEAR::SOAP not suitable for > > speaking with default-.NET services > > - When or will this be available > > I thought it did that already. Perhaps I did not look carefully at the > implemented CVS code. Take a look for yourself, but I think Shane also > mentioned that this is there in the msg you quoted. Oops, sorry, I wasn't completely awake the answer was POSITIVE: > > > PEAR::SOAP does support doc/lit. > > * There is not much documention > > - Will this be enhanced, or who can give some inside pointers (without > > refactoring the source) on the implementation > > In principle you could run phpdocumentor on the SOAP code and get javadoc-like > API docs. Apart from the source code, the SOAP_Interop examples, the talks by > Shane at talks.php.net and the text that someone in this list has written, > there is no other (known to me) userland documentation with detailed stepwise > examples. Actually and I'am trying to figure out all the necessary information on PEAR::SOAP to set up some kind of cook-book, starting with an easy client, to a complex server with samples of interoperation between PHP, .NET and Java. That's where all the questions come from.. I want to have a clear picture first, then I can do the job i hate the most, but is surely necessary. I think with the push of MS.NET, PHP and SOAP will boost in the coming year. I am thinking of a documentationset with pointers to simple explanations about WebServices and SOAP, starting a simple server and client. Add more complexity to it. Add other "languages" . The talks are a good startingpoint, but the code is not always "error" free. So one clear set of files, should make life easier for a lot of interested people.. > > + How is the WSDL binding arranged and how does it function > > + What are the benefits of implementing an "__dispatch($method)" method > > in the Service ? > > > > I hope somebody can clarify this? > > /me points to Shane for those last items. /me looks into the direction of Shane... Klaasjan... http://klaasjan.tukker.org