S
Simon L. Prinsloo
Guest
I suspected as much, but hoped there was a way that I could override the behaviour. The prototype used a static dataset that essentially simply "extended" the SOAP, so the Android client could get to anything it needed using the SOAP object it received, but now the structure changed. They want as little data as possible crossing the wire due to mobile network issues and costs. I've now written the Dataset to a longchar and reparsed it with SAX, writing out only the bare essentials that we need throug a SAX writer and returned that as a LONGCHAR, but now the SOAP have a single "CDATA" node in the output parameter, instead of the structure, which means they now nead to import another API in the Android app to parse this "string" as an XML object.
Continue reading...
Continue reading...