On question 1, the message you show is:
org.jibx.runtime.JiBXException: Expected
"{http://ws.si.com/schemas/ws/appendixb}parentForecast"; end tag, found
"{http://ws.si.com/schemas/ws/ab}parent-zip"; end tag (line 1, col 141)This is referencing two different namespaces, while the document only has one. The problem is probably in your binding definition, with the use of namespaces.
On question 2, you should be able to use the same JiBX bound classes for both sides of your interaction, assuming that's what you want to do. The binding file is up to you - if you want you can use different classes and a correspondingly different binding definition, so long as the XML representation is the same.
- Dennis
Dennis M. Sosnoski Enterprise Java, XML, and Web Services Training and Consulting http://www.sosnoski.com Redmond, WA 425.885.7197
babloosony wrote:
Hi Dennis,
Thank you for the kind response.
1. I am using JiBX on client side and server side to access a web service. However I face some exceptions in the JiBX AXIS DeSerializer on client side. I have below soap request message, soap response message and exception on client side:
soap request message
----------------------------------
<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> <soapenv:Body> <getWeather xmlns="http://ws.ab.com/wsdl/ws/ab";> <ziprq>343434</ziprq> </getWeather> </soapenv:Body>
</soapenv:Envelope>
soap response message
------------------------------------
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
<soapenv:Body>
<getWeatherResponse xmlns="http://ws.si.com/wsdl/ws/ab";>
<forecast xmlns="http://ws.si.com/schemas/ws/ab"; hi="0"
low="0" precip="0">
<parentForecast>
<parent-zip>520010</parent-zip>
</parentForecast>
<zip>343434</zip>
<city>Campbell</city>
<state>CA</state>
<date>April 11, 2003</date>
<forecast>20 percent chance of rain.</forecast>
<temp>
<temp>35</temp>
</temp>
<vectorElement>INDIA</vectorElement>
<vectorElement>CHINA</vectorElement>
<vectorElement>JAPAN</vectorElement>
</forecast>
</getWeatherResponse>
</soapenv:Body></soapenv:Envelope> exception on client side
--------------------------------------
org.jibx.runtime.JiBXException: Expected
"{http://ws.si.com/schemas/ws/appendixb}parentForecast"; end tag, found
"{http://ws.si.com/schemas/ws/ab}parent-zip"; end tag (line 1, col 141)
2. Now my second question is, do we need to seperate version of AXIS-JiBX (De)Serializers on client side and server side and if so why & do we need same (version) of JiBX binding xml file on client side and server side ?
Thanks once again for the kind response.
Kumar.
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ jibx-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jibx-users
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ jibx-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jibx-users
