axis-c-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From krishna <kris...@lac.uic.edu>
Subject Re: Regarding desearilizing problem of GoogleSearch API response...
Date Fri, 20 Jan 2006 00:53:39 GMT
Hi

I faced a similar problem sometime back. I do not know whether it has 
been resolved in the 1.6 build.
You can look up

http://www.mail-archive.com/axis-dev@ws.apache.org/msg05383.html

for reference

Thanks
Krishna


Ashutosh Kumar wrote:

> Hi,
> I am using axis C++ stubs to use Google API and I am able to send receive
> SOAP data from the server. While deserializing the received data from the
> server, the Deserializer is failing.
>
> The received SOAP data from Google server is as follows
> ******************************************************************
> <?xml version=3D'1.0' encoding=3D'UTF-8'?>
> <SOAP-ENV:Envelope xmlns:SOAP-ENV=3D" 
> http://schemas.xmlsoap.org/soap/envelo=pe/" xmlns:xsi=3D" 
> http://www.w3.org/1999/XMLSchema-instance" 
> xmlns:xsd=3D"http://www.w3.org/1999/XMLSchema" 
> <http://www.w3.org/1999/XMLSchema%22>>
> <SOAP-ENV:Body>
> <ns1:doGoogleSearchResponse xmlns:ns1=3D"urn:GoogleSearch"
> SOAP-ENV:encodingStyle=3D" http://schemas.xmlsoap.org/soap/encoding/">
> <return xsi:type=3D"ns1:GoogleSearchResult">
> <directoryCategories xmlns:ns2=3D" 
> http://schemas.xmlsoap.org/soap/encoding/=
> "
> xsi:type=3D"ns2:Array" ns2:arrayType=3D"ns1:DirectoryCategory[1]">
> <item xsi:type=3D"ns1:DirectoryCategory">
> <fullViewableName
> xsi:type=3D"xsd:string">Top/Regional/Asia/India/Guides_and_Directories</ful=
> lViewableName>
> <specialEncoding xsi:type=3D"xsd:string"></specialEncoding>
> </item>
> </directoryCategories>
> <documentFiltering xsi:type=3D"xsd:boolean">false</documentFiltering>
> <endIndex xsi:type=3D"xsd:int">10</endIndex>
> <estimateIsExact xsi:type=3D"xsd:boolean">false</estimateIsExact>
> <estimatedTotalResultsCount
> xsi:type=3D"xsd:int">28600000</estimatedTotalResultsCount>
> <resultElements xmlns:ns3=3D" http://schemas.xmlsoap.org/soap/encoding/"
> xsi:type=3D"ns3:Array" ns3:arrayType=3D"ns1:ResultElement[10]">
> <item xsi:type=3D"ns1:ResultElement">
> <URL xsi:type=3D"xsd:string">
> http://www.cia.gov/cia/publications/factbook/geos/in.html 
> <http://www.cia.gov/cia/publications/factbook/geos/in.html></URL>
> <cachedSize xsi:type=3D"xsd:string">101k</cachedSize>
> <directoryCategory xsi:type=3D"ns1:DirectoryCategory">
> <fullViewableName xsi:type=3D"xsd:string"></fullViewableName>
> <specialEncoding xsi:type=3D"xsd:string"></specialEncoding>
> </directoryCategory>
> <directoryTitle xsi:type=3D"xsd:string"></directoryTitle>
> <hostName xsi:type=3D"xsd:string"></hostName>
> <relatedInformationPresent
> xsi:type=3D"xsd:boolean">true</relatedInformationPresent>
> <snippet xsi:type=3D"xsd:string">Features a map and brief descriptions of
> geography, economy, government, and people.</snippet>
> <summary xsi:type=3D"xsd:string"></summary>
> <title xsi:type=3D"xsd:string">CIA - The World Factbook --
> &lt;b&gt;India&lt;/b&gt;</title>
> </item>
> </resultElements>
> <searchComments xsi:type=3D"xsd:string"></searchComments>
> <searchQuery xsi:type=3D"xsd:string">india</searchQuery>
> <searchTime xsi:type=3D"xsd:double">0.131947</searchTime>
> <searchTips xsi:type=3D"xsd:string"></searchTips>
> <startIndex xsi:type=3D"xsd:int">1</startIndex>
> </return>
> </ns1:doGoogleSearchResponse>
> </SOAP-ENV:Body>
> </SOAP-ENV:Envelope>
> *******************************************************************
>
> While deserializing this file the axis deserializer crashes in the 
> function
> getcmplxobj() after executing the function
> checkmessge("doGoogleSearchResponse","urn:GoogleSearch").
>
> In axisdeserializer() while deserializing "documentfiltering" and 
> checking
> the return type with XSD__BOOLEAN, it is getting XSD_UNKNOWN and is 
> finally
> setting exception in the function getXSDtype(). Inside this function 
> that i=
> t
> starts checking is "DirectoryCategory" instead of "documentfiltering" 
> which
> is the currentnode at that time. Please provide some insight into the 
> error
> and the probable solution.
> Thanks for extending help..
> Ashutosh Kumar
>
>
>


Mime
View raw message