Edit report at https://bugs.php.net/bug.php?id=50956&edit=1

 ID:                 50956
 Updated by:         s...@php.net
 Reported by:        tony at marston-home dot demon dot co dot uk
 Summary:            SOAP-ERROR: parsing schema
-Status:             Open
+Status:             Feedback
 Type:               Bug
 Package:            SOAP related
 Operating System:   Windows XP
 PHP Version:        5.2.12
 Block user comment: N
 Private report:     N

 New Comment:

Could you provide the full WSDL that exhibits this behavior?


Previous Comments:
------------------------------------------------------------------------
[2010-06-16 01:00:40] rvestra at unm dot edu

Can anyone provide feedback on this it would really help?  I am running across 
the same problem.  I get this error on the documentation tag as follows.

"SOAP-ERROR: Parsing Schema: unexpected <documentation> in schema"

------------------------------------------------------------------------
[2010-02-07 19:10:28] tony at marston-home dot demon dot co dot uk

Description:
------------
I am calling a soap service using the WSDL supplied by the service provider, 
but it is failing when I try to create the soap client. The error message is:

SOAP-ERROR: Parsing Schema: unexpected <annotation> in element


Reproduce code:
---------------
The wsdl file contains entries such as:

<xs:complexType name="FWTAuditDetails">
  <xs:annotation>
    <xs:documentation>
    blah blah blah
    </xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="Created" type="xs:dateTime" minOccurs="0" />
    <xs:element name="CreatedBy" type="FWTUser" minOccurs="0" />
    <xs:element name="LastModified" type="xs:dateTime" minOccurs="0" />
    <xs:element name="LastModifiedBy" type="FWTUser" minOccurs="0" />
  </xs:sequence>
</xs:complexType>

If I put '<!--' and '-->' around the <xs:annotation> element the error 
disappears.


Expected result:
----------------
As the <annotation> element is merely there for documentation purposes it 
should be ignored instead of causing an error.



------------------------------------------------------------------------



-- 
Edit this bug report at https://bugs.php.net/bug.php?id=50956&edit=1

Reply via email to