I think you will have to write your own XMLDecoder. You won't be the first user to have to write a custom decoder. This is not my area of expertise, but AIUI, unless you are using SOAP or otherwise have a WSDL or descriptor, the existing decoders must guess the type of each attribute and child in the XML data. The most common case is when an array has only one value in it. Since the default conversion is going guess wrong about any string that looks like a number, your choices are to fix that by special-casing the conversion, or repairing the data after conversion.
If you have lots of fields that will be wrong, it will probably be more efficient to write your own decoder. Set the resultType to e4x and be the first one to handle the complete event, walk through the XML and convert it to ObjectProxy (or better yet, a custom Value Object). If there are only a few conversions, you could just be first to handle the complete event, and walk through each ObjectProxy and convert the Number back into a String, assuming you can reliably do that. HTH, -Alex On 11/21/17, 8:56 PM, "AbdulSakeer" <sakeer.sm...@gmail.com> wrote: >Hi, > >Could anyone help me on this. I am still stuck with this. > >- Abdul Sakeer > > > >-- >Sent from: >https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle >x-users.2333346.n4.nabble.com%2F&data=02%7C01%7C%7Cd3d2cdf899e4485a302908d >531656f57%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636469234133158356& >sdata=izbTZVKj6%2FdwCrllk9MFfTpPnjRTT8udW0S1zvPrJPU%3D&reserved=0
