This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
RE: xalan-j2 D7: StreamSource cannot be kept?
- To: <xsl-list at lists dot mulberrytech dot com>
- Subject: RE: [xsl] xalan-j2 D7: StreamSource cannot be kept?
- From: "Michael Kay" <mhkay at iclway dot co dot uk>
- Date: Fri, 10 Aug 2001 12:08:55 +0100
- Reply-To: xsl-list at lists dot mulberrytech dot com
>
> "Michael Kay" <mhkay@iclway.co.uk> wrote:
> > The JAXP 1.1 spec is rather remiss in that it doesn't say
> which kinds of
> > Source object are consumed by supplying them to a
> transformation. But I
> > think it's reasonable to assume that a StreamSource or
> SAXSource can only
> be
> > used once.
>
> Hmm... you really ought to be able to use a Source as many
> times as you wish (even if the JAXP 1.1 spec is not specific about it).
What I really meant was that in supplying a StreamSource as the input to a
transformation, you expect the state of the underlying InputStream to
change. Are you suggesting that the processor should mark() the current
position of the underlying InputStream at the time it is supplied, and
reset() that position on completion? What if markSupported() for the
InputStream is false?
Even then, there seem to be other things in the contract that have been left
unspecified, for example I think the processor can reasonably expect that
no-one else will be reading bytes off the InputStream at the same time...
Mike Kay
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list