Facebook
Twitter
P
Patrick M
Guest
I am a new user of the Plesk API and I was struck by the problematic schema validations.
One rather curious validation exception I got was because I reused the same code to generate the inner elements of a Client/add and a Client/set xml requests.
When revising the schema, I understood that the exception was thrown because the sequence order was not respected:
ADD: <hosting> comes before <limits>
SET: <hosting> comes after <limits>
Working around this situation involves making two specific routines for the two calls, not very pleasant when doing maintenance.
Any ideas regarding this ?
One rather curious validation exception I got was because I reused the same code to generate the inner elements of a Client/add and a Client/set xml requests.
When revising the schema, I understood that the exception was thrown because the sequence order was not respected:
ADD: <hosting> comes before <limits>
SET: <hosting> comes after <limits>
Working around this situation involves making two specific routines for the two calls, not very pleasant when doing maintenance.
Any ideas regarding this ?
