| Subject: | "element.tt NOT_FOUND error - no type found" for type-less elements |
| Date: | Tue, 13 Sep 2011 10:48:55 +0200 |
| To: | bug-SOAP-WSDL [...] rt.cpan.org |
| From: | Patrick <patrick.kuijvenhoven [...] gmail.com> |
Elements that do not have a type fail with "element.tt NOT_FOUND error
- no type found"
Test results are the same for SVN-trunk, 2.00.99_3 and 2.00.10
According to the spec, it's allowed to have type-less elements:
http://www.w3.org/TR/xmlschema-1/#declare-element and specifically
this quote: "Note that the above allows for two levels of defaulting
for unspecified type definitions. An <element> with no referenced or
included type definition will correspond to an element declaration
which has the same type definition as the head of its substitution
group if it identifies one, otherwise the ·ur-type definition·. This
has the important consequence that the minimum valid element
declaration, that is, one with only a name attribute and no contents,
is also (nearly) the most general, validating any combination of text
and element content and allowing any attributes, and providing for
recursive validation where possible."
Workaround: Add "<xsd:complexType/>" to definition
Attachments: MyService-fails fails, MyService-success.wsdl (containing
the work-around) succeeds
Message body is not shown because sender requested not to inline it.
Message body is not shown because sender requested not to inline it.