G
Guest
Hello all,
I'm working on a web app that we converted over to asp 2.0 recently and
here's the issue I ran into:
We use a java webservice to retrieve data and display this data to the user.
This was working in 1.1 and nothing changed around this particular webservice
call on either side after the switch to 2.0. The webservice response is an
array of value objects and the value object contains a boolean. I intercepted
the response with Fiddler and verified that the boolean was set to either
true or false on all the vo's in the array. But after the response object was
created and I could look at it in the code while debugging, the (nullable)
boolean field in every vo in the array was null.
To fix this temporarily, I had the webservice provider change the boolean
field to a 'NullableBoolean' class that contained a boolean value - this way,
the correct value came across and I could work with it.
I'm not sure if this is helpful, but there's one more detail I noticed -
The xml doc I intercepted with Fiddler looks something like this
('processed' is the boolean variable):
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"...>
<env:Body env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
....
<responseVos...>
....
<ResponseVo ...>
....
<processed href="#ID_4"/>
....
</ResponseVo>
....
</responseVos...>
....
<xsd:boolean xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xsi:type="xsd:boolean" id="ID_4">true</xsd:boolean>
....
</env:Body>
</env:Envelope>
This is working for now but I think I shouldn't have to have my webservice
provider fix my problem, right? Any help in solving this problem would be
greatly appreciated.
I'm working on a web app that we converted over to asp 2.0 recently and
here's the issue I ran into:
We use a java webservice to retrieve data and display this data to the user.
This was working in 1.1 and nothing changed around this particular webservice
call on either side after the switch to 2.0. The webservice response is an
array of value objects and the value object contains a boolean. I intercepted
the response with Fiddler and verified that the boolean was set to either
true or false on all the vo's in the array. But after the response object was
created and I could look at it in the code while debugging, the (nullable)
boolean field in every vo in the array was null.
To fix this temporarily, I had the webservice provider change the boolean
field to a 'NullableBoolean' class that contained a boolean value - this way,
the correct value came across and I could work with it.
I'm not sure if this is helpful, but there's one more detail I noticed -
The xml doc I intercepted with Fiddler looks something like this
('processed' is the boolean variable):
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"...>
<env:Body env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
....
<responseVos...>
....
<ResponseVo ...>
....
<processed href="#ID_4"/>
....
</ResponseVo>
....
</responseVos...>
....
<xsd:boolean xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xsi:type="xsd:boolean" id="ID_4">true</xsd:boolean>
....
</env:Body>
</env:Envelope>
This is working for now but I think I shouldn't have to have my webservice
provider fix my problem, right? Any help in solving this problem would be
greatly appreciated.