On 09/28/11 09:55, azurIt wrote:
> Because it is not checking parameters count (even if i use Mandatory types
> (or setting arguments like 'nillable' by hand)) and it is not validating
> types so, for example, if you send string to integer parameter, you gets HTTP
> error 500 :( i will have to explain users when this happen that they are
> sending invalid parameters. On the opposite, they will be notified on this by
> server with 'hard' validation enabled.
>
the soft validation is not supposed to accept arbitrary strings for
integer arguments. it also should verify {min,max}_occurs and nillable
properties. if it doesn't respect the constraints, it's a bug. please
provide a self-contained test case that illustrates the problem in the
issue tracker so that i can work on it.
soap-wrapped-by-http standard dictates HTTP 500 for any kind of error.
the client should parse the faultcode element to see whether the error
is the client's or the server's fault. the faultcodes for soft
validation and lxml validation are Client.ValidationError and
Client.SchemaValidationError respectively. if that's not the case for
any kind of validation error, it's a bug. again, provide a
self-containted test case that illustrates this in a separate issue so
that i can fix it.
hth,
burak
> ______________________________________________________________
>> Od: "Burak Arslan" <[email protected]>
>> Komu: azurIt <[email protected]>
>> Dátum: 28.09.2011 07:02
>> Predmet: Re: [Soap-Python] lxml validation is too restrictive
>>
>> CC: [email protected]
>> On 09/27/11 23:44, azurIt wrote:
>>> Any ideas how to keep input validating (number of parameters and it's
>>> types) but also support at least SUDS + PHP soap client ?
>> why doesn't the 'soft' validator work for you?
>>
> _______________________________________________
> Soap mailing list
> [email protected]
> http://mail.python.org/mailman/listinfo/soap
_______________________________________________
Soap mailing list
[email protected]
http://mail.python.org/mailman/listinfo/soap
