Axis webservice may be asked to deliver invalid XML characters

We've had a case where it seems that the axis webservice is being asked by confluence to transmit characters that are not valid in an XML response. (Bytes below 0x20 except for 0x9, 0xA and 0xD)

While the case in question makes it appears that control characters are making their way into the Confluence index that perhaps shouldn't, we probably should investigate make the webservice filter these characters appropriately so that RPC response don't fail entirely.

This is possible in Axis by providing a different XML character encoding strategy and configuring the library to use it.

I'd suggest looking at replacing these invalid code points with a question mark or similar.