Hi, well, this is one solution... although I am not happy with the idea of patching Xerces whenever a new version comes out. Anyway, I will give it a try.
Thanks so far! Marco Hi Marco, You could try applying the patch attached to the JIRA issue. I haven't reviewed it, but it apparently resolves the problem. Thanks. Michael Glavassevich XML Parser Development IBM Toronto Lab E-mail: mrgla...@ca.ibm.com E-mail: mrgla...@apache.org Winter Marco <marco.win...@esolutions.de> wrote on 07/16/2010 02:27:43 AM: > Hi Michael, > > Thanks for this information. But, what is the right way to handle > this issue? So far, I patched my DocBook stylesheets so they take > the right relative path. But I don't think this is the preferred solution. > > Greetings > Marco > Hi Marco, > > Winter Marco <marco.win...@esolutions.de> wrote on 07/15/2010 11:12:26 AM: > > > Hello, > > > > I am using Apache FOP (svn) together with Xerces2-J 2.7.1 to create > > PDF files out of DocBook documents. My problem is that FOP cannot > > find images included in "second-level" DocBook files included with > > XInclude. After some investigation, I found that the issue seems to > > be the same as discussed in the Jira issue XERCESJ-1102 (https:// > > issues.apache.org/jira/browse/XERCESJ-1102). As in that scenario, > > the values of the <xml:base> tags are malformed and contain relative > > paths to the master document instead of the direct parent. > > > > Using the latest version of Xerces2-J didn't solve the problem. So I > > wonder if this bug hasn't been fixed already as mentioned in the ticket? > > Xerces-J 2.10.0 still has this bug. I see there's a patch attached > to the JIRA issue but it hasn't been reviewed yet. > > > Thanks, > > Marco > > Thanks. > > Michael Glavassevich > XML Parser Development > IBM Toronto Lab > E-mail: mrgla...@ca.ibm.com > E-mail: mrgla...@apache.org