On Mar 4, 2008, at 15:02, Fournier,Danny [NCR] wrote:
Hi
I'm really at a loss here. Here's the full exception message:
Notes
- several lines complaining about the required content model
Yes, but AFAICT they all point to one and the very same error.
- "44 more ---------" in the middle of the exception - 44 more
required
content model errors?
No. "44 more..." simply means "this stack trace was cut off and is
actually longer (contains 44 more calls)"
So, no need to worry there. You have one and only one error.
Long shot, but given the below sample code you posted:
public String setXSLT(String strXSLT){
try{
this.xslt = new ByteArrayInputStream(strXSLT.getBytes
("ISO-8859-1"));
return "";
} catch(UnsupportedEncodingException uee) {
return getStackTrace(uee);
}
}
This could lead to encoding headaches. The String's bytes are forced
to IS0-8859-1. Further on, when the BAIStream is used again and
wrapped into say an InputStreamReader (say by the XSLT processor,
maybe?), unless the encoding is forced there too, the JVM could
assume your default platform encoding, or the XML default of UTF-8 to
determine which character they represent...
My guess is that the FO actually contains such wrongly encoded
characters/bytes, and this is causing weird errors (?)
As stated above, a long shot, but well worth a try. The above is not
the best of programming practices anyway, especially if the stream
will be consumed by a component/module not under your control.
Cheers
Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
