Thanks all of you for your tips. I don't know the cause, but as the output is correctly generated, finally I've opted to create a log filter to filter out all the messages with its lengthy call stack (it is time consuming and generates really very big log files).
-----Mensaje original----- De: Conal Tuohy [mailto:[EMAIL PROTECTED] Enviado el: martes, 20 de abril de 2004 0:39 Para: [EMAIL PROTECTED] Asunto: RE: SAXParseException: Content is not allowed in prolog. David, it sounds like your mystylesheet.xsl has some content in the prolog. Are you sure there's nothing wrong there? It's easy to accidentally insert some white space at the start of the file or something. > -----Original Message----- > From: Carmona Perez, David [mailto:[EMAIL PROTECTED] > Sent: Tuesday, 20 April 2004 2:36 a.m. > To: Cocoon (E-mail) > Subject: RV: SAXParseException: Content is not allowed in prolog. > > > > Hi, > > If I save the result of the xinclude processing to a file and > do the following: > > <map:read src="xincludedfile.xml"/> > <!--Till here XML received is well formed--> > <map:transform type="saxon" src="mystylesheet.xsl"/> > <map:generate type="html"/> > > then everything goes ok. > > This seems a bug of the XInclude transformer. > > Has this happened to anyone else? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ************************************************************* Este correo ha sido procesado por el antivirus del Grupo FCC. ************************************************************* ************************************************************* Este correo ha sido procesado por el antivirus del Grupo FCC. ************************************************************* --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
