DO NOT REPLY [Bug 24844] New: - XMLByteStreamCompiler.getSAXFragment() shouldn't return whole array

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24844>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24844

XMLByteStreamCompiler.getSAXFragment() shouldn't return whole array

           Summary: XMLByteStreamCompiler.getSAXFragment() shouldn't return
                    whole array
           Product: Cocoon 2
           Version: Current CVS 2.1
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: core
        AssignedTo: dev@cocoon.apache.org
        ReportedBy: peter.brant@courts.state.wi.us


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.

I first noticed the problem with a transform like this:

            <map:transform src="cocoon:/generate-page">
              <map:parameter name="dn" value="{request-param:dn}" />
            </map:transform

This still works fine though (???):

      <map:match pattern="test">
        <map:generate src="test.xml" />
        <map:transform src="test.xslt" />
        <map:serialize />
      </map:match>

Re: DO NOT REPLY [Bug 24844] New: - XMLByteStreamCompiler.getSAXFragment() shouldn't return whole array

[Torsten Curdt <tc...@vafer.org>]

> 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