Re: HELP : xsi:null="true"

2002-03-13 Thread dovle

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 to do so. But 'til then I 
think it is a bug. :o(((

HOw I have discovered that : using the tag 
 

instead of simply using the 
 


For those who use ksoap as client: I have solved this by modifying the class 
SOAPWriter in order to check if attribute is null. If so, then does not write 
the attribute at all. It was already done this, but comented ( // ) 

Thanks again for helping me ,
dovle 

> 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 ':name' using encoding style
> 'http://schemas.xmlsoap.org/soap/encoding/'.
>
> Now I think I might know why does it reacts this way: my tag where it fails
> looks like this :
> 
> As you can see, there is no xsi:type. And maibe (here I need your
> confirmation because I haven't worked too much with apache soap) the apache
> soap checks the type first and after that checks if it is a null object.
> Might be an apache 'bug'. (haven't read all the specs about soap, but ...)
>
> I will try to check if this is the cause and if so I will inform you if so.
>
> Thanks for all,
> dovle
>
> > I ran into a problem using Apache SOAP 2.2 within WSAD (WebSphere Studio
> > Application Developer IDE).  To solve it the Apache SOAP jar had to
> > appear before WSAD's webcontainer.jar in the CLASSPATH.  There was a
> > method conflict that caused the null objects to deserialize to objects
> > built with the default constructor.  You may have a similar conflict in
> > one of your jar files.



Re: HELP : xsi:null="true"

2002-03-13 Thread dovle

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 ':name' using encoding style 
'http://schemas.xmlsoap.org/soap/encoding/'.

Now I think I might know why does it reacts this way: my tag where it fails 
looks like this :

As you can see, there is no xsi:type. And maibe (here I need your 
confirmation because I haven't worked too much with apache soap) the apache 
soap checks the type first and after that checks if it is a null object. 
Might be an apache 'bug'. (haven't read all the specs about soap, but ...)

I will try to check if this is the cause and if so I will inform you if so.

Thanks for all,
dovle  

> I ran into a problem using Apache SOAP 2.2 within WSAD (WebSphere Studio
> Application Developer IDE).  To solve it the Apache SOAP jar had to appear
> before WSAD's webcontainer.jar in the CLASSPATH.  There was a method
> conflict that caused the null objects to deserialize to objects built with
> the default constructor.  You may have a similar conflict in one of your
> jar files.



Re: HELP : xsi:null="true"

2002-03-13 Thread hughes_shawn


I ran into a problem using Apache SOAP 2.2 within WSAD (WebSphere Studio
Application Developer IDE).  To solve it the Apache SOAP jar had to appear
before WSAD's webcontainer.jar in the CLASSPATH.  There was a method
conflict that caused the null objects to deserialize to objects built with
the default constructor.  You may have a similar conflict in one of your
jar files.

Shawn.



   
  
   
  
  [EMAIL PROTECTED] To:  [EMAIL PROTECTED]   
  
   cc: 
  
  03/13/2002 10:53 Subject: Re: HELP : xsi:null="true" 
  
  AM   
  
  Please respond   
  
  to soap-user 
  
   
  
   
  



On Wednesday 13 March 2002 12:05, you wrote:
> Its xsi:nil and not xsi:null for specifying that an element value holds a
> null value...

dovle pretty sad to disappoint you but this is the answer that I am
reveiving
from my apache soap when an attribute has null value: (snapshot from
UtilSnoop)


 http://xml.apache.org/xml-soap";
xsi:type="ns3:Vector"
 xsi:null="true"/>
 
 0
 http://schemas.xmlsoap.org/soap/encoding/";
 xsi:type="ns4:Array" ns4:arrayType="xsd:boolean[]"
xsi:null="true"/>

Are you shure that you receive the xsi:nil="true" ?

I have read the Soap specification and I have found the same :

A NULL value or a default value MAY be represented by omission of the
accessor element. A NULL value MAY also be indicated by an accessor element

containing the attribute xsi:null with value '1' or possibly other
application-dependent attributes and values.  (Quoting from W3C specs for
ksoap1.1)

So what could be wrong inhere ?

Has anyone managed to send an struct object with null attribute values ? (I

believe you have but ...)

TIA for your answers
dovle





This communication is for informational purposes only.  It is not intended as
an offer or solicitation for the purchase or sale of any financial instrument
or as an official confirmation of any transaction. All market prices, data
and other information are not warranted as to completeness or accuracy and
are subject to change without notice. Any comments or statements made herein
do not necessarily reflect those of J.P. Morgan Chase & Co., its
subsidiaries and affiliates.




Re: HELP : xsi:null="true"

2002-03-13 Thread dovle

On Wednesday 13 March 2002 12:05, you wrote:
> Its xsi:nil and not xsi:null for specifying that an element value holds a
> null value...

dovle pretty sad to disappoint you but this is the answer that I am reveiving 
from my apache soap when an attribute has null value: (snapshot from 
UtilSnoop)


http://xml.apache.org/xml-soap"; xsi:type="ns3:Vector" 
xsi:null="true"/>

0
http://schemas.xmlsoap.org/soap/encoding/";
xsi:type="ns4:Array" ns4:arrayType="xsd:boolean[]" xsi:null="true"/>

Are you shure that you receive the xsi:nil="true" ? 

I have read the Soap specification and I have found the same :

A NULL value or a default value MAY be represented by omission of the 
accessor element. A NULL value MAY also be indicated by an accessor element 
containing the attribute xsi:null with value '1' or possibly other 
application-dependent attributes and values.  (Quoting from W3C specs for 
ksoap1.1)

So what could be wrong inhere ? 

Has anyone managed to send an struct object with null attribute values ? (I 
believe you have 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 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 contains some null values and is serialized like this
> > 
> > 0
> > 
> > 
> > 
> > 
> >
> > (is part of a Vector, of course)
> >
> > On serverside I get the following exception :
> > No mapping found for ':name' using encoding style
> > 'http://schemas.xmlsoap.org/soap/encoding/'.
> >
> > When I send a TestSerizable with a name but with valid == null then I get
> > the same exception, but for :valid . And so on.
> >
> > Does apache soap 2.2 knows to use xsi:null (even if using schema 1999) ?
> > I have tried with schema 2000 and still the same .
> >
> > Or else, what is wrong inhere ? I have no idea.
> >
> > Please , need quick help, deadline comming :o(
> > dovle
>
> 
> This email and any files transmitted with it are confidential and
> intended solely for the use of the individual or entity to whom
> they are addressed. Any views or opinions are solely those of
> the author and do not necessarily represent those of Exel
> Computer Systems plc. If you have received this email in error
> please notify Customer Services on 0115 946 0101.
> 



RE: HELP : xsi:null="true"

2002-03-13 Thread Colin Saxton

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 

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 contains some null values and is serialized like this
> 
> 0
> 
> 
> 
> 
>
> (is part of a Vector, of course)
>
> On serverside I get the following exception :
> No mapping found for ':name' using encoding style
> 'http://schemas.xmlsoap.org/soap/encoding/'.
>
> When I send a TestSerizable with a name but with valid == null then I get
> the same exception, but for :valid . And so on.
>
> Does apache soap 2.2 knows to use xsi:null (even if using schema 1999) ? I
> have tried with schema 2000 and still the same .
>
> Or else, what is wrong inhere ? I have no idea.
>
> Please , need quick help, deadline comming :o(
> dovle



This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom
they are addressed. Any views or opinions are solely those of
the author and do not necessarily represent those of Exel
Computer Systems plc. If you have received this email in error
please notify Customer Services on 0115 946 0101.




Re: HELP : xsi:null="true"

2002-03-12 Thread dovle

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 contains some null values and is serialized like this
> 
> 0
> 
> 
> 
> 
>
> (is part of a Vector, of course)
>
> On serverside I get the following exception :
> No mapping found for ':name' using encoding style
> 'http://schemas.xmlsoap.org/soap/encoding/'.
>
> When I send a TestSerizable with a name but with valid == null then I get
> the same exception, but for :valid . And so on.
>
> Does apache soap 2.2 knows to use xsi:null (even if using schema 1999) ? I
> have tried with schema 2000 and still the same .
>
> Or else, what is wrong inhere ? I have no idea.
>
> Please , need quick help, deadline comming :o(
> dovle