The link you cite is misleading.  It it also to information for using deployment 
descriptor type mappings, which is the standard way to add your mapping.  There is no 
documentation for subclassing the SOAPMappingRegistry class that I know of.  You would 
need to read the source code for that class yourself to figure out how to subclass it.

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: Tuesday, August 24, 2004 4:57 AM
Subject: AW: Intger as Parameter does not allow null


> hi Scott,
> I have some trouble with the soap documentation:
> I looked under the topic Creating Type Mappings and found following
> 
> Registering Type Mappings on the Server
> ...
> For information about overriding the default mapping registry, look here.
> 
> 
> when I klick at 'here' I arrive at the following
> 
> Specifying Type Mappings in a Deployment Descriptor
> 
> which is not quite the thing what I have expected
> 
> the next link here directs you to the top of the page.
> 
> can you help me finding the expected Docs?
> 
> thanks in advance
> 
> 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
>

Reply via email to