Hi. I am in the process to upgrade a DocBook application to FOP 0.93 and have run into a problem regarding Catalog resolver. In the documentation I have read about how to set Catalog- (URI-) resolvers either on the fopFactory (fopFactory.setURIResolver) and/or foUserAgent (foUserAgent.setURIResolver) and I have tried both. In a moment of desperation I also tried to set it on my transformer (transformer.setURIResolver). However to no avail. What happens is that the <!DOCTYPE-reference is bypassed from resolving and the result is a time-out. If I comment out the <!DOCTYPE however all other references (in the stylesheets and such) are resolved however. I also tried to extend the Resolver just to be able to see the references and, as I thought, there are none. I am using org.apache.xml.resolver.tools.CatalogResolver.CatalogResolver() which used to work allright in fop 0.25. Does anybody have any information regarding this I would be most grateful. Regards
Lars Bjerges Vi ber dig lägga märke till att detta e-postmeddelande kan innehålla konfidentiell information. Om du felaktigt blivit mottagare av detta meddelande ber vi dig informera avsändaren om felet genom att använda svara-funktionen. Vi ber dig också att radera e-postmeddelandet utan att skicka det vidare eller kopiera det. Trots att vi intygar att e-postmeddelandet och eventuella bilagor inte innehåller virus och andra fel som kan påverka datorn eller IT-systemet där det mottages och läses, öppnas det på mottagarens eget ansvar. Vi tar inte på oss något ansvar för förlust eller skada, som har uppstått i samband med att e-postmeddelandet mottagits och använts. _____________________________________________________________________________________________________________________________________________________________ Please note that this message may contain confidential information. If you have received this message by mistake, please inform the sender of the mistake by sending a reply, then delete the message from your system without making, distributing or retaining any copies of it. Although we believe that the message and any attachment are free from viruses and other errors that might affect the computer or IT system where it is received and read, the recipient opens the message at his or her own risk. We assume no responsibility for any loss or damage arising from the receipt or use of this message.
