Hi Marius, I'm experiencing problems similar to yours: I am quite sure the problem is in the fact that, by default, JiBX thinks that OTA XML messages must respect the order of elements as given in the schemas, whereas it is not so. I'm writing a web service server about this, and 2 well known companies in the field send OTA messages with a different order of elements.
The solution I found was to modify the binding.xml file and add a ordered="false" attribute in the tags (<mapping> or <structure>) offended by the incoming message. It works, but it is boring, because it seems it cannot be stated one time for all at codegen time that, to me, order is not important. Please see the paragraph "Mixing it up" in http://jibx.sourceforge.net/tutorial/binding-extras.html Hope this helps. Cheers, Vito Meuli Marius-Cristian Vasilescu wrote: > > I've ran into two common errors, but I couldn't find a solution. The first > one occurs when I get a fault message because of the extra "faultactor" > tag. > Should I add something for fault handling? Adding > "soapClient.addInFaultDetailsHandler(new ExceptionReader());" didn't help. > > org.jibx.ws.WsException: Error reading end of fault. > Root cause: org.jibx.runtime.JiBXException: Expected "{ > http://schemas.xmlsoap.org/soap/envelope/}Fault"; end tag, found > "faultactor" > start tag > > ..... > <soap:Body> > <soap:Fault> > <faultcode>soap:Client.3100</faultcode> > <faultstring>Authentication Error</faultstring> > <detail> > <text>Invalid or missing credentials</text> > </detail> > <faultactor>security_manager</faultactor> > </soap:Fault> > </soap:Body> > .... > > In the second case there is an error because of the missing "EchoData" > tag, > just after <Success/>. I think OTA specifications require EchoData or at > least the OSGi built requires it, but the server response doesn't contain > the tag. Is there any way to handle such errors without changing > binding.xml > and recompile everything? ..because there are so many dependencies. What > would you recommend? > > org.jibx.ws.WsException: Error in unmarshalling. > Root cause: org.jibx.runtime.JiBXException: Expected "{ > http://www.opentravel.org/OTA/2003/05}EchoData"; start tag, found "{ > http://www.opentravel.org/OTA/2003/05}OTA_PingRS"; end tag > > .... > <soap:Body> > <OTA_PingRS EchoToken="REQ.A1454.2231" PrimaryLangID="en-us" > TimeStamp="2011-04-14T12:21:38+02:00" Version="1.005" xmlns=" > http://www.opentravel.org/OTA/2003/05";> > <Success/> > </OTA_PingRS> > </soap:Body> > -- View this message in context: http://old.nabble.com/faultactor-error---jibx-ota-tp31398643p31688651.html Sent from the jibx-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ vRanger cuts backup time in half-while increasing security. With the market-leading solution for virtual backup and recovery, you get blazing-fast, flexible, and affordable data protection. Download your free trial now. http://p.sf.net/sfu/quest-d2dcopy1 _______________________________________________ jibx-users mailing list jibx-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jibx-users
