Thanks.  This was due to the line break normalization code.  Should be
fixed.

BTW, what I did with line break normalization: chars could be coming from
multiple docs, all with different sorts of line breaks.  The current Xerces
serializers allow content to go out with odd mixes of line break
characters.  What I do in the transition code is catch this at a fairly low
level, and make sure everything is normalized.  I think this is the right
thing.  This needs to be done at a bit higher lever in the serializer code,
but I don't have time to track all the issues at the moment.

-scott




                                                                                                                   
                    Sebastien                                                                                      
                    Sahuc                To:     cocoon-dev@xml.apache.org, xalan-dev@xml.apache.org               
                    <ssahuc@imedi        cc:     (bcc: Scott Boag/CAM/Lotus)                                       
                    ation.com>           Subject:     RE: [Xalan2][C2] DOM2DOM issue .                             
                                                                                                                   
                    10/04/00                                                                                       
                    11:53 AM                                                                                       
                    Please                                                                                         
                    respond to                                                                                     
                    xalan-dev                                                                                      
                                                                                                                   
                                                                                                                   





> -----Original Message-----
> From: Scott Boag/CAM/Lotus [mailto:Scott_Boag@lotus.com]
> Sent: Wednesday, October 04, 2000 5:42 PM
> To: xalan-dev@xml.apache.org
> Cc: cocoon-dev@xml.apache.org
> Subject: Re: [Xalan2][C2] DOM2DOM issue .
>
>
>
> > Therefore it more than enough since the reported problem
> > only affect DOM (Davanum is right that the DOM2DOM isn't properly
> working, I
> > checked today with the lastest snapshot).
>
> Sorry not to be fully keeping up on the mails.  What is the problem in
> Xalan with DOM2DOM?
>
> > There is also a problem (ArrayOutOfBound Exception) with
> the 'in-house'
> > serializing of trax.
>
> Can you give me a stack dump?

You'll find a stack trace attached...

Basicaly I'm trasforming the foo.xml and foo.xsl sent previously by Davanum
(sitemap.xmap and sitemap.xsl from a cocoon2 poitn of view), but couldn't
reproduce it with simple test since it makes use of extension (so needs
cocoon.jar, bsf.jar, etc...)

Here is the piece of code that 'brings out' the bug :

      Templates templates = processor.process(new
InputSource(this.getClass().getResourceAsStream("foo.xsl")));
      Transformer transformer = templates.newTransformer();
      InputSource in = new
InputSource(this.getClass().getResourceAsStream("foo.xml"));
      transformer.transform(in , new Result(new StringWriter()));  // <---
RT exception thrown HERE

>
> Also: what are you guys doing with xsl:output in Cocoon2?  The output
> properties need to be passed to the serailizer.  Please, please, fix
> this....

Don't worry, I'm just writing TestCase using the JUNIT framework, and
occasonaly I need to serialize to check if everything is as expected, no
more no less.


>
> -scott
>
>
>
>
>
>
>                     Sebastien
>
>                     Sahuc                To:
> cocoon-dev@xml.apache.org
>                     <ssahuc@imedi        cc:
> xalan-dev@xml.apache.org, (bcc: Scott Boag/CAM/Lotus)
>                     ation.com>           Subject:
> [Xalan2][C2] DOM2DOM issue .
>
>
>                     10/04/2000
>
>                     11:21 AM
>
>                     Please
>
>                     respond to
>
>                     xalan-dev
>
>
>
>
>
>
>
>
> > Davanum, please check out the latest Xalan, without your
> > patches, and see
> > how that does.  It should handle both the NodeIterator issue and the
> > extension bugs (I hope).  I'll try and do some testing
> > against your files
> > sometime tonight, and take a look at your patches to see what didn't
> > overlap or where you had a better idea on how to do
> something than I.
> >
>
> Well I'm working right now to remove all DOM from the XSP
> engine, so the
> latest Xalan2 snapshot is just working fine when it comes to SAX 2 SAX
> transformation. Therefore it more than enough since the
> reported problem
> only affect DOM (Davanum is right that the DOM2DOM isn't
> properly working,
> I
> checked today with the lastest snapshot).
>
> There is also a problem (ArrayOutOfBound Exception) with the
> 'in-house'
> serializing of trax. But I wasn't able to reproduce the bug
> outside the
> cocoon2 context, so I ended up using the serialize package
> (which is by the
> way a piece of art ! ).
>
> All the best,
>
> Sebastien
>
>
>
>
>
>
>
>