Testing results :
It seems that I was right: apache soap checks first if there is a xsi:type
present ? If yes then checks if it can resolve it and after that it checks
for the xsi:null attribute. From my viewpoint, this seems to me not to be the
preffered order... but maibe they have a reason
On Wednesday 13 March 2002 18:42, you wrote:
Simple as this:
I use ksoap as client and apache soap as server. Send from apache soap a
struct with xsi:null="true" for some attribs and the apache soap sais that
cannot deserialize the attribute . with the following message:
No mapping found for ':
cc:
03/13/2002 10:53 Subject: Re: HELP : xsi:null="true"
ave but ...)
TIA for your answers
dovle
>
> -Original Message-
> From: dovle [mailto:[EMAIL PROTECTED]]
> Sent: 12 March 2002 20:12
> To: [EMAIL PROTECTED]
> Subject: Re: HELP : xsi:null="true"
>
>
> Not mentioned:
> using orion 5.2
> apache so
Its xsi:nil and not xsi:null for specifying that an element value holds a
null value...
-Original Message-
From: dovle [mailto:[EMAIL PROTECTED]]
Sent: 12 March 2002 20:12
To: [EMAIL PROTECTED]
Subject: Re: HELP : xsi:null="true"
Not mentioned:
using orion 5.2
apache soap 2.2
Not mentioned:
using orion 5.2
apache soap 2.2
And the TestSerializable is registered to the BeanSerializer
Please help !!!
> Problems encontered and don't know if this is apache's fault or I am doing
> something wrong.
>
> I send the message as xml schema 1999 .
>
> I have a bean that conta
