Re: [fw-webservices] Strict typing and WS-I standards compliance

I just took the auto-generated WSDL and modified it by hand to be WS-I
compliant, with the help of someone far more familiar with WSDL than me.

That being said, I have to use the Zend_Soap_Autodiscover still, as PHP's
SoapClient (and Z_S_Client as well since it's really just a wrapper for
SoapClient) doesn't work properly with WS-I compliant WSDL files. I believe
it is related to another of the patches you submitted in JIRA. Strangely,
SoapServer seems to have no issue with them.

Bugzilla from fabien@crespel.net wrote:
>
> neen wrote:
>> I'm setting up a SOAP Web Service that is going to be accessed from an
>> ASP.NET box. I'm currently using Zend_Soap_Autodiscover. I'm trying to
>> resolve several errors:
>>
>> R2716 [...] R2204 [...] R2210 [...] R2710
>>
>> Does anyone have any suggestions on how to fix the above errors when
>> using
>> Zend_Soap_Autodiscover? Am I SOL?
>
> I have been working on these problems for a personal project for a while,
> and
> just proposed several patches to improve Zend_Soap_*. You can find the
> main patch
> in http://framework.zend.com/issues/browse/ZF-6349 but make sure to check
> this
> issue's dependencies and related issues.
>
> Another solution for you would be to try the rpc-literal style instead of
> document-literal. The WSDL generated by Zend_Soap_AutoDiscover in this
> case is
> still not WS-I compliant, but less changes are needed to make it comply
> (add a
> namespace attribute to the operation's input and output elements).
>
> - Fabien.
>
>
>

--
View this message in context: http://www.nabble.com/Strict-typing-and-WS-I-standards-compliance-tp23119915p23152418.html
Sent from the Zend Web Services mailing list archive at Nabble.com.