On 03/09/2017 04:23 PM, nobili, philippe wrote:

We stumbled across a different URI-related issue using the JNLP deployed 
version of XXE-7.3, we wondered if it adds a new light on the URI path 
problem... Unfortunately, this one is a complete blocker :(.

We fail to convert DocBook4 books onto PDF with the JNLP deployed version of 
XXE-7.3; we got the following error message from FOP:

Converting XSL-FO file "__doc.fo" to "__doc.pdf" using FOP
FOP XSL-FO processor error:
java.lang.IllegalArgumentException: URI is not absolute

I cannot reproduce this problem. I have no problem converting a DocBook V4 (or V5) document to PDF using FOP, when XXE v7.3 is deployed using Java Web Start.





The DocBook4 document itself has not changed and can be converted successfully 
into PDF using the JNLP deployed version of XXE-6.3, which is the version that 
we currently use in production.  The JNLP deployment uses the deployment tool 
provided with XXE and is therefore the same as for the previous version of XXE.

Is there any chance that the URI file path management has changed since XXE 6.3 
?

No.




--> *Ancient* versions of FOP had problems with image URIs which were not absolute. That's why in *ancient* versions of XXE, there was a workaround (in the process command used to convert DocBook to PDF) for this FOP bug.

In recent versions of FOP, the bug is fixed and we have removed the workaround from the process command:

In XXE v7.3, but also in XXE v6.3, there is NO workaround to absolutize the URIs of image resources:
---
  <command name="docb.toPS">
    <process>
    ...
      <copyDocument to="__doc.xml">
        ...
        <resources include="image"
                   match="(?:.+/)?(.+)\.(png|jpg|jpeg|gif|mml|svg|svgz%1)"
                   copyTo="resources" referenceAs="resources/$1.$2" />
---

That's the only problem I recall related to FOP and absolute URIs.



--> If you have customized the process command used to convert DocBook to PDF and/or customized the DocBook XSL stylesheets and/or use an old version of the FOP add-on (currently we use Apache FOP 2.1; see http://www.xmlmind.com/xmleditor/addons_doc.html#fop1_foprocessor), please do not hesitate to send me (mailto:huss...@xmlmind.com) your customizations.




--
XMLmind XML Editor Support List
xmleditor-support@xmlmind.com
http://www.xmlmind.com/mailman/listinfo/xmleditor-support

Reply via email to