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

[Gerald Wiesinger]

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 at documit                                             
             e.com>                                                     To 
             Sent by:                  <xep-support at 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 at 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,4c2cfaf5496921411022863!
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: parser_error.txt
URL: <http://lists.renderx.com/pipermail/xep-support/attachments/20100701/884fb991/attachment.txt>