AW: Intger as Parameter does not allow null

hello Scott,
thanks for the hint

Malte

-----Ursprüngliche Nachricht-----
Von: Scott Nichol [mailto:[email protected]]
Gesendet: Montag, 23. August 2004 22:49
An: [email protected]
Betreff: Re: Intger as Parameter does not allow null


To my knowledge, you can send a null xsd:int, but you cannot receive one
(and I believe the message below is from receiving such a null).

To receive a null xsd:int, you must write a new deserializer and map it to
xsd:int .

Scott Nichol

Do not send e-mail directly to this e-mail address,
because it is filtered to accept only mail from
specific mail lists.
----- Original Message -----
From: "Malte Kempff" <[email protected]>
To: <[email protected]>
Sent: Monday, August 23, 2004 4:57 AM
Subject: Intger as Parameter does not allow null


> Hello,
> I would very much have the possibility to send an Integer as Parameter,
> which could be null.
> unfortunately soap gives me this error:
>
> SOAP-RPC:[Attributes={}] [faultCode=SOAP-ENV:Client] [faultString=Cannot
set
> null value for primitive type int] [faultActorURI=/soap/servlet/rpcrouter]
> [DetailEntries=] [FaultEntries=] Fault Code=SOAP-ENV:Client
>
> I don't like to use a dummy Integer for that matter.
> Why does Apache SOAP does not differenciate between int and Integer as
> paramaeter, does AXIS do it?
>
> Malte
>
> ____________
> Virus checked by G DATA AntiVirusKit
> Version: AVK 14.0.1937 from 18.08.2004
> Virus news: www.antiviruslab.com
>
>

____________
Virus checked by G DATA AntiVirusKit
Version: AVK 14.0.1937 from 18.08.2004
Virus news: www.antiviruslab.com