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

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: A document-literal binding in a DESCRIPTION MUST NOT have the
namespace a
ttribute specified on contained soapbind:body, soapbind:header,
soapbind:headerf
ault and soapbind:fault elements.

R2204: A document-literal binding in a DESCRIPTION MUST refer, in each of
its so
apbind:body element(s), only to wsdl:part element(s) that have been defined
usin
g the element attribute.

R2210: If a document-literal binding in a DESCRIPTION does not specify the
parts
attribute on a soapbind:body element, the corresponding abstract
wsdl:message M
UST define zero or one wsdl:parts.

R2710: The operations in a wsdl:binding in a DESCRIPTION MUST result in wire
sig
natures that are different from one another. An endpoint that supports
multiple
operations must unambiguously identify the operation being invoked based on
the
input message that it receives. This is only possible if all the operations
spec
ified in the wsdl:binding associated with an endpoint have a unique wire
signatu
re.

Does anyone have any suggestions on how to fix the above errors when using
Zend_Soap_Autodiscover? Am I SOL?
--
View this message in context: http://www.nabble.com/Strict-typing-and-WS-I-standards-compliance-tp23119915p23119915.html
Sent from the Zend Web Services mailing list archive at Nabble.com.