Hi
Apache SOAP2.2 checks for 'Null' values (when using SOAP-encoding style)
by checking for the attribute "xsi:null=true".
(see encoding/soapenc/SoapEncUtils.java:isNull(Element))
The SOAP 1.1 spec says that NULL values are represented by setting the
xsi:null attribute value to "1".
i.e., "xsi:
ns/ideas
...
thanx
-john
- Original Message -
From: "Karappan, Raju M" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, April 05, 2002 12:41 PM
Subject: RE: null handling in apache soap2.2
>
> Aache SOAP is expecting xsi:null='true' instead of
Interesting ... Any schema experts that can confirm that "xsi:null='1' " is
invalid ?
thanx
-john
- Original Message -
From: "Karappan, Raju M" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, April 05, 2002 11:41 AM
Subject: RE: null h
om: John Mani [SMTP:[EMAIL PROTECTED]]
> Sent: Friday, April 05, 2002 12:48 PM
> To: [EMAIL PROTECTED]
> Subject: Re: null handling in apache soap2.2
>
> > This looks like a null object to me, with xsi:null='1':
> >
> >
> > Wouldn't an empty Person
> This looks like a null object to me, with xsi:null='1':
>
>
> Wouldn't an empty Person object look like
>
Yup, that's what I thought too .. a bug in Apache SOAP ? Or are we
missing something ?
(btw, Sun's JAX-RPC implemetation also exhibits similar behaviour)
-john
>
>
>
>
Interestingly enough, my client writting using the JAX-RPC RI code from
Sun also exhibits this same behaviour ... i.e., getting an 'empty' Person
object instead of just null
-john
> Hi
>
> I'm implementing an apache SOAP client that interacts with a WebLogic 6.1
> sp2
> based SOAP server applica
This looks like a null object to me, with xsi:null='1':
Wouldn't an empty Person object look like
"John Mani"
John,
I ran into the same problem. In my case, there was a conflict in the
webcontainer.jar file from IBM. I don't know what the conflict was, but
moving the Apache SOAP jar file above webcontainer.jar in my runtime
classpath solved the problem. It sounds like you have a similar conflict
