I would have to agree. AMF is much easier to get up and running and (I feel) is more object oriented.
I would be inclined to use WebOrb or ZendAMF (Part of the Zend Framework): http://www.themidnightcoders.com/products/weborb-for-php http://framework.zend.com/download/amf --- In [email protected], "Nate Beck" <n...@...> wrote: > > Yea, if you're WSDL is public facing, I'll see if I can create a Flex Client > against it as well. > On a similar note... Have you looked into AMFPHP (http://www.amfphp.org/)? > SOAP is a great standard but, like everything, there are issues with it. > If you are only using your SOAP webservice to talk to Flex / Flash > front-ends, then I'd recommend having a look at AMF. However, if you're > using your webservices with other technologies, SOAP might be a better > option. > > HTH, > Nate > > On Tue, Jan 6, 2009 at 6:44 AM, valdhor <valdhorli...@...> wrote: > > > Can you post a link to the wsdl and I can see if I can get a Flex > > client working. > > > > > > --- In [email protected] <flexcoders%40yahoogroups.com>, "ocslhk" > > <martin.kaberg@> wrote: > > > > > > Hello, > > > > > > This is my first post here and the first time i use yahoo groups. I > > > have searched for something similar on the boards but haven't found it. > > > > > > Anyway I am quite new flex and I'm building my first app real app. I > > > have an app running on a php server, and I'm using soap to communicate > > > with flex. I am also using the cairngorm framework. Everything have > > > been worked smooth until now. I have a few methods on the soap server > > > that recieves VOs. But some of VOs I cant use as arguments. I have no > > > idea why. Even if i create a new obj using just one property that is a > > > string it doesn't work. But i does work via the php soap client. > > > > > > When i look at the xml it is slightly different between php and flex > > > soap clients, but the definition of the VO is identical. > > > > > > From php: > > > <?xml version="1.0" encoding="UTF-8"?> > > > <SOAP-ENV:Envelope > > > xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"; > > > xmlns:ns1="http://singingfish.localhost"; > > > xmlns:xsd="http://www.w3.org/2001/XMLSchema"; > > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > > > xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"; > > > SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";> > > > <SOAP-ENV:Body> > > > <ns1:testPriceVO> > > > <p xsi:type="ns1:Price_VO"> > > > <amount xsi:type="xsd:string"></amount> > > > <end_time xsi:type="xsd:string"></end_time> > > > <id xsi:type="xsd:string"></id> > > > <name xsi:type="xsd:string"></name> > > > <priority xsi:type="xsd:string"></priority> > > > <short_name xsi:type="xsd:string"></short_name> > > > <start_time xsi:type="xsd:string"></start_time> > > > </p> > > > </ns1:testPriceVO> > > > </SOAP-ENV:Body> > > > </SOAP-ENV:Envelope> > > > > > > from flex > > > <SOAP-ENV:Envelope > > > xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"; > > > xmlns:xsd="http://www.w3.org/2001/XMLSchema"; > > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> > > > <SOAP-ENV:Body > > > SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";> > > > <ns1:testPriceVO xmlns:ns1="http://singingfish.localhost";> > > > <p xsi:type="ns1:Price_VO"> > > > <amount xsi:type="xsd:string"></amount> > > > <end_time xsi:type="xsd:string"></end_time> > > > <id xsi:type="xsd:string"></id> > > > <name xsi:type="xsd:string"></name> > > > <priority xsi:type="xsd:string"></priority> > > > <short_name xsi:type="xsd:string"></short_name> > > > <start_time xsi:type="xsd:string"></start_time> > > > </p> > > > </ns1:testPriceVO> > > > </SOAP-ENV:Body> > > > </SOAP-ENV:Envelope> > > > > > > I have tried using both soap 1.1 and soap 1.2 on the php client and it > > > works the same. > > > > > > > > > > > > > -- > > Cheers, > Nate > ---------------------------------------- > http://blog.natebeck.net >
