Myriam,
I resolved the problem. I supplied blank localName and not blank qName
to all startElement(), endElement() etc. It was working fine with Xalan
1.x and Xalan 2 up to D7. So I fixed that and it seems to be backward
compatible with Xalan 1.x
I wonder if you should test if local is blank and do something?
Thank you
Alex
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, August 14, 2001 12:25 PM
> To: [EMAIL PROTECTED]
> Subject: RE: [ANNOUNCE] Xalan-J 2.2.D9 Released! Having
> strange problems
>
>
>
> Alex,
> I think we'd still like to take a look at the sequence of SAX
> events you
> are producing. All of our SAX samples and API tests are
> passing (I just
> double checked), so I'm thinking that you are probably doing something
> we're not.
> Obviously, we are getting the events from the parser which is
> exactly what
> you are not doing.
> There were some changes to namespace processing, maybe
> something there is
> causing the failures. I think we're relying on namespace
> events as both
> attributes and startPrefix events (as required by SAX). Joe
> can tell you
> more about this.
> Since this is failing with any document, maybe you can send
> us a short 10
> lines document with your code reproducing the failure? I'll
> try to see what
> I can find out on my end.
>
> Thanks,
> Myriam
>
>
>
>
> "Roytman,
>
> Alex" To:
> <[EMAIL PROTECTED]>
> <roytmana@peac cc: (bcc: Myriam
> Midy/CAM/Lotus)
> etech.com> Subject: RE:
> [ANNOUNCE] Xalan-J 2.2.D9
> Released! Having
> strange problems
> 08/14/01 11:29
>
> AM
>
> Please respond
>
> to xalan-dev
>
>
>
>
>
>
>
>
>
> Myriam,
>
> This problem does not depend on xml or xsl structure. All
> transformations which fail are from SAX events I produce myself rather
> than from parsed file. If I serialize my SAX to xml file and
> then apply
> the same stylesheet it works fine.
> Even simplest stylesheet (default2.xsl in xalan distribution) fails It
> actually produces output but it garbled
> Attached normal.html - output I would expect (produced from a
> file) and
> bad.html (produced directly from SAX)
> I would like to mention that serialization transform still works fine
> for me
>
>
> PS as I said it happens with all stylesheets and all xml (when using
> SAXSource) and does not happen when parsing the same XML from
> a file so
> I did not attach xml/xsl - xml has somewhat confidential data. Please
> let me know if you need it
>
> Thank you very much
>
> Alex Roytman
> [EMAIL PROTECTED]
>
> > -----Original Message-----
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> > Sent: Tuesday, August 14, 2001 9:48 AM
> > To: [EMAIL PROTECTED]
> > Subject: RE: [ANNOUNCE] Xalan-J 2.2.D9 Released! Having
> > strange problems
> >
> >
> >
> > I'm not sure what would be the problem. Maybe the changes to
> > the systemID
> > resolver? Can you send us an example of a failing
> stylesheet, xml and
> > calling program if one is used?
> >
> > Myriam
> >
> >
> >
> >
> > "Roytman,
> >
> > Alex" To:
> > <[EMAIL PROTECTED]>
> > <roytmana@peac cc: (bcc: Myriam
> > Midy/CAM/Lotus)
> > etech.com> Subject: RE:
> > [ANNOUNCE] Xalan-J 2.2.D9
> > Released! Having
> > strange problems
> > 08/13/01 07:27
> >
> > PM
> >
> > Please respond
> >
> > to xalan-dev
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Hello,
> >
> > What has changed since D7?
> >
> > Almost none of my stylesheets /* which work fine with Xalan
> 2D7, Xalan
> > 1.2.2 */ work any more.
> > Any ideas? I am getting no error messages whatsoever
> >
> > Thank you very much
> >
> > Alex
> (See attached file: attach.zip)
>
>
