Huge status produced when setting empty input source in Filter Stream Converter application

It produce a 450M files and need more than 1G of temporary RAM to do it.

The issue come from the server input stream which is put in the job request and which is serialized.

Ideas:

• customize the serialization of any InputStream/OutputStream at XStream level (and probably not serialize anything, or just a toString())
• customize the serialization of any InputSource/OutputSource at XStream level (and probably not serialize anything, or just a toString())
• customize the serialization of FilterStreamConverterJobRequest at Serialize level