change testClient to use local wsdl about sbml-mod-ws HOT 3 CLOSED

I never tried to work with the testClient, so I leave the details to you. It looks like you may enter a local path in the this style: Client('file:///path/to/file') (see here)
See the second answer for use of a relative path.

from sbml-mod-ws.

Of course I had tried that already and can load via file:///... the wsdl file.
Loading the SBMLedit wsdl file from http://cbu.bioinfo.no/wsdl/SBMLedit.wsdl locally works fine, however, it contains the links to esysbio and needs an online connection nevertheless, whereas the wsdl file, which was already present in the sbmlmod folder from the very beginning does not work at all.
The testClient itself works fine, it just needs to be executed.

Thus, the issue is purely concerning the wsdl description.

from sbml-mod-ws.

With commit 88d6468 I circumvent calling client.service.ValidateSBMLModelGzippedBase64Encoded entirely, as this call causes an ZSI error ZSI:EvaluateException Got None for nillable(False), minOccurs(1) element (None,ModelIsValid).
Instead, the files are decompressed and decoded and send to ValidateSBMLModelText instead, which works fine (as does ValidateSBMLModelBase64Encoded if no compression is chosen).
Sadly, I couldn't figure out, what causes the server side error, but for now this solution works fine. If you agree, we can close this issue.

Note that changing nillable=False -> nillable=True in ValidateSBMLModelGzippedBase64EncodedResponse_Dec of src/sbmlmod/SBMLmod_types lets the script run smoothly, but it reports non validity of the resulting models, which is incorrect.

from sbml-mod-ws.