Search WSDL invalid?

[michel.weber]

Hi a nagging bug that i noticed in Webinator+ 5.1.86 and that is still there in 5.1.87 (WSDl V1.37 2009/09/11)

The WSDL contains a 'minoccurs' for an attribute declariation which is not valid.<xsd:complexType name="metasearchTarget">

<xsd:simpleContent>
<xsd:extension base="xsd:string">
<xsd:attribute name="selected" type="xsd:string" minOccurs="0"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>

JAVA libraries (axis) and other soap request generators complain about this and we have to do manual editing of the WSDL everytime we have to regenerate the classes.

[jason112]

Yes, the minOccurs on the attribute is something that has already been fixed internally, and will be part of the next scripts release.

[michel.weber]

There seems to be other problems with the WSDL.
It does not seem to specify all the elements.
For example the <parametric query> element is missing for common-request.

Again this causes problems with JAVA libraries, or at least complicate matters for developpers.

Also in the common response the user-specified parametric query is not present, but the one specified in the profile, which is a bit misleading.

[michel.weber]

The minoccurs is fixed in V 5.1.88

>> Yes, the minOccurs on the attribute is something that has already been fixed
>> internally, and will be part of the next scripts release.

[jason112]

> For example the <parametric query> element is missing for common-request.

Correct, user-overriding parametric queries have not yet been added to the SOAP interface, and will be added in an update. Specifying the individual "qp" parameters is possible with "Param" elements, though.

> Also the user-specified parametric query is not present, but the one specified in the profile, which is a bit misleading.

If a user query is provided, then yes it should be outputted rather than the one on the profile. This will probably be a behavior change with an update (we'll provide through your existing ticket).