Hi Matthias, The way we've implemented the interface, you can be completely in control of how HTTP is authenticated by implementing o.a.f.apps.io.ResourceResolver[1] and giving it to the FopFactoryBuilder/FopConfParser[2].
As for the base URI for fonts, you can set this in the fop-conf, we haven't created a way to set this programmatically, that was an oversight on our end. I'll enable a way to do this and get back to you. [1] http://wiki.apache.org/xmlgraphics-fop/URIResolution [2] http://wiki.apache.org/xmlgraphics-fop/FopFactoryConfiguration Hope that helps, Mehdi On 24 July 2012 00:01, Matthias Reischenbacher <matthias8...@gmx.at> wrote: > Hi, > > I just tried to upgrade to latest trunk and noticed two compatibility > issues with my application which I couldn't fix on my own: > > * The fontManager has no setBaseURL method anymore. How is the base URL > set now? > > * The FOURIResolver class doesn't exist anymore. Sub classing it for > applying HTTP basic authentication parameters is therefore not possible. > See also: http://wiki.apache.org/**xmlgraphics-fop/HowTo/** > BasicHttpAuthentication<http://wiki.apache.org/xmlgraphics-fop/HowTo/BasicHttpAuthentication> > How is HTTP authentication handled now? > > Thanks for your help, > Matthias > > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: > fop-users-unsubscribe@**xmlgraphics.apache.org<fop-users-unsubscr...@xmlgraphics.apache.org> > For additional commands, e-mail: > fop-users-help@xmlgraphics.**apache.org<fop-users-h...@xmlgraphics.apache.org> > >
