[XalanJ2] baad output SAX events generated by Xalan2J

[Sebastien Sahuc <ss...@imediation.com>]

Hello,

The SAX events generated by Xalan2 are not XML conformance :-)

Indeed this is the SAX Events I get from the result transformation (I put a
TraceXMLFilter between the Tranformer and the Serializer) :

  startPrefixMapping(test, "http/uri/test")
  startDocument
  startElement(code)
  endDocument()

The problem is, as you can see by yourself, that the prefix mapping events
are not sent at the right time, neither there is a endPrefixMapping event
for closing.

I didn't noticed the problem before (though I was getting crazy not
understanding which on my filters was corrupting the SAX stream...), but
this issue need be be *urgently* fix before we -at cocoon2- can integrate
Xalan2 in the code.

I'm sure this is related to Dims' problem.

Thanks,

Sebastien


> -----Original Message-----
> From: Scott Boag/CAM/Lotus [mailto:Scott_Boag@lotus.com]
> Sent: Wednesday, October 11, 2000 5:43 AM
> To: xalan-dev@xml.apache.org
> Subject: Re: XalanJ2 Extensions fixes uploaded
> 
> 
> 
> > extend14, extend15 -- These are awaiting the nodeset 
> extension which, in
> > turn, is waiting for Scott to look at XRTreeFrag.nodeset() 
> and see what
> > should be done with that.
> 
> Gary L Peskin <ga...@firstech.com> wrote:
> Keep reminding me.  My next priority for the next couple of 
> days before
> Alpha is to take a look at performance.  I'll try and 
> remember to take a
> look at XRTreeFrag.nodeset() also.
> 
> > Scott, do you think that once xsl:include is
> > working
> > for me, we can make this option invalid?
> 
> Yes.
> 
> -scott
> 
> 
> 
> 
>