XMLByteStreamCompiler.getSAXFragment() has been changed recently to return the whole array instead of creating a new array trimmed to the appropriate length.
This causes problems for (at least) XMLByteStreamInterpreter which spews as many startDocument() events as there are zeroes at the end of the array. This causes Saxon to throw an exception.
Thanks for reporting! -- Torsten
