Many weeks no problems, now java.lang.ClassCastException

My MSN search application had been working fine for many weeks. This morning, without having made any changes, I'm getting the following error (in Java-based CFML application):

AxisFault faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException faultSubcode: faultString: java.lang.ClassCastException faultActor: faultNode: faultDetail: {http://xml.apache.org/axis/}stackTrace:java.lang.ClassCastException at org.apache.axis.message.SOAPFaultBuilder.onEndChild(SOAPFaultBuilder.java:299) at org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1090) at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerce...

I've gone through my SOAP request line by line to make sure it's corresponding to the latest WSDL, and to me everything looks OK. Has anything changed today with the service/WSDL that could be the culprit?

Many thanks for any suggestions.

[1315 byte] By [wynfred] at [2008-2-27]
# 1

Turns out this issue was solved simply by getting a new appid for the MSN Search API. Since others have had similar experiences (inexplicable errors solved by getting a new appid), I'd like to know why this happened. Was there something about the way I was using the service that caused the appid to be banned? I've reviewed the terms of service and can't see why there would be any problems with the way I was using it.

wynfred at 2007-9-9 > top of Msdn Tech,Windows Live Developer Forums,Windows Live Search: Development...

Windows Live Developer Forums

Site Classified