RE: [xep-support] Problem rendering XEP internal format to PDF

I'll give it a try and let you know the results...thanks for the response.
--- Glenn Pearson

-----Original Message-----
From: owner-xep-support@renderx.com [mailto:owner-xep-support@renderx.com]
On Behalf Of Gerald Wiesinger
Sent: Thursday, July 01, 2010 3:32 AM
To: xep-support@renderx.com
Subject: [xep-support] Problem rendering XEP internal format to PDF

Glenn,

i have been able to reproduce this error with your code. in our environment
(WAS) we can avoid this by instantiating the XMLReader with

XMLReader xmlreader = XMLReaderFactory.createXMLReader();

in addition we are using the embeddedimagefilter

xmlreader.setContentHandler(new EmbeddedImageFilter(contentHandler,
getLogger()));

____________________________________
Best Regards
Gerald Wiesinger

                                                                           
             "Glenn Pearson"
             <gpearson@documit
             e.com> To
             Sent by: <xep-support@renderx.com>
             owner-xep-support cc
             @renderx.com
                                                                   Subject
                                       [xep-support] Problem rendering XEP
             30.06.2010 21:21 internal format to PDF
                                                                           
                                                                           
             Please respond to
             xep-support@rende
                  rx.com
                                                                           
                                                                           

We are having a problem in a specific customer environment (Tomcat) that is
difficult to change (such as what classes are being loaded and in what
order). All calls to XEP work fine, except the calls that render from the
intermediate (XEP) format to PDF. I have attached a file that contains
details of the trace from xep-debug.jar. We suspect the problem has to do
with xerces, but we don't know. The same code works fine in all other
environments that I have tested it in.

I believe the code is pretty much exactly as recommend by an example in the
API delivery. We are stumped and are switching from the API to command
line interface (which works fine), unless we can find a solution.
--- Glenn Pearson

 (See attached file: parser_error.txt)

!DSPAM:28,4c2d3215496922100511882!

-------------------
(*) To unsubscribe, send a message with words 'unsubscribe xep-support'
in the body of the message to majordomo@renderx.com from the address
you are subscribed from.
(*) By using the Service, you expressly agree to these Terms of Service http://www.renderx.com/terms-of-service.html
Received on Thu Jul 1 10:59:50 2010