Luis Bernardo <lmpmbernardo <at> gmail.com> writes: > > > Probably the URI is validated during the XML/XSL to FO transformation, > and the validation requires a call -- you can check that by returning an > invalid response. In any case, the official input for FOP is FO and the > caching was implemented with that in mind. > > You can tweak your URIResolver to not call the DB and just return an > "OK" response the first time it is called for a particular URI. > > You can tweak your URI resolver
Thanks for your reply. I'll probably move towards doing the XSLT transformation in a separate step then. The source XML data is generated on database side so performing the transformation to FO there is an option. Note that I've only associated the URIResolver with the FOUserAgent and *not* with the Transformer so I'm still wondering why the URIResolver is invoked while doing the XSLT transformation. Regards. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
