This is the mail archive of the xsl-list@mulberrytech.com mailing list .

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: SAXParseException

From: Trevor Nash <tcn at melvaig dot co dot uk>
To: xsl-list at lists dot mulberrytech dot com
Date: Wed, 28 Aug 2002 11:54:26 +0100
Subject: Re: [xsl] SAXParseException
Organization: Melvaig Software Engineering Limited
References: <200208261802.g7QI2Cus030279@chilled.skew.org> <1030387216.1655.18.camel@localhost.localdomain> <roimmu4c8nu6p4fsig5o0240ha7l36g132@4ax.com> <1030461197.1655.28.camel@localhost.localdomain>
Reply-to: xsl-list at lists dot mulberrytech dot com

>That would be a good guess, but I'm not doing it programatically. I'm
>using COCOON to do the processing, passing in the XSL and the XML from a
>JSP. 
>
>Any other ideas?

Then it is possible the JSP is wrong - perhaps sometimes you generate
a faulty XML or XSL from that.  Is there some way you can look at the
XML and XSL to check it is what you think it is?

Trevor
--
Traditional training & distance learning,
Consultancy by email

Melvaig Software Engineering Limited
voice:     +44 (0) 1445 771 271 
email:     tcn@melvaig.co.uk

 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list

Follow-Ups:
- Re: SAXParseException
  - From: Manish Shah

References:
- Re: Why processor or stylesheets puts strange output
  - From: Mike Brown
- SAXParseException
  - From: Manish Shah
- Re: SAXParseException
  - From: Trevor Nash
- Re: SAXParseException
  - From: Manish Shah

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]